Hello,
Sorry for the non explicit title but I couldn't be clear!
I am new with this but I know some stuff about android like I know Kernels, Recovery, ROM etc.
However, I was wondering these things, I am not up to date:
1) What is UBER?
2) What can contain a Kernel that a Rom can't? Is the Kernel like the heart and the ROM more like the body? It's sometimes really ambiguous for me
3) WTF Is that external memory system lol, is that possible to use the external SD and move some apps without formatting it only for the phone?
4) I like CM 13, really like it and especially because of the Theme that you can change and who change now everything and not only the desktop °_° but I was wondering what kernel should I use with CM13, I mean like a specific kernel who could be better than the CM Base
5) I tried many roms, CM, Beanstalk, DominionOS but in every case I coudn't get a functional GAPPS, with OpenApps Aroma I don't have the Playstore, with the A-GAPSS I have it but it crashes sometimes (play service fc ++edit: i will watch for permission > result: it still doesn't work and fc++) and this is like I can't use snapchat because of this... Any idea about this?
Thanks to all, have a nice day
Kicroy said:
Hello,
Sorry for the non explicit title but I couldn't be clear!
I am new with this but I know some stuff about android like I know Kernels, Recovery, ROM etc.
However, I was wondering these things, I am not up to date:
1) What is UBER?
2) What can contain a Kernel that a Rom can't? Is the Kernel like the heart and the ROM more like the body? It's sometimes really ambiguous for me
3) WTF Is that external memory system lol, is that possible to use the external SD and move some apps without formatting it only for the phone?
4) I like CM 13, really like it and especially because of the Theme that you can change and who change now everything and not only the desktop °_° but I was wondering what kernel should I use with CM13, I mean like a specific kernel who could be better than the CM Base
5) I tried many roms, CM, Beanstalk, DominionOS but in every case I coudn't get a functional GAPPS, with OpenApps Aroma I don't have the Playstore, with the A-GAPSS I have it but it crashes sometimes (play service fc ++edit: i will watch for permission > result: it still doesn't work and fc++) and this is like I can't use snapchat because of this... Any idea about this?
Thanks to all, have a nice day
Click to expand...
Click to collapse
1) Uber? It is a taxi service... https://play.google.com/store/apps/details?id=com.ubercab&hl=en
2) The kernel is essentially the interface between the OS and the hardware, so your analogy is very accurate.
3) I am not sure what you asking about external storage... it is the SD card when it is in Portable mode. (assuming Marshmallow) you cannot install apps to it in portable mode (external). This should give you what you need to know: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/109134/p/1449,9582
4) There is no "best kernel"... kernels are always a trade off, performance for battery life and vis-versa, the best anyone can tell you is try and see which works best for you. Remember to dirty flash ROM between trying different custom kernels to fix any changes to the ram disk and other /boot changes by the previous kernel.
5) Ask in the ROM thread for the recommended Gapps package for each ROM, if the recommended one doesn't work, then post in that thread and you should get feedback.
Hey thanks man!
Uber as a kernel thing I mean is that something godlike like linaro was in the old time?
Oh so the "problem" about moving things like in older phone is about 6.0 and not about the phone himself?
Hmm okay I will try them so!
And gonna ask cm post then, thanks
Kicroy said:
Hey thanks man!
Uber as a kernel thing I mean is that something godlike like linaro was in the old time?
Oh so the "problem" about moving things like in older phone is about 6.0 and not about the phone himself?
Hmm okay I will try them so!
And gonna ask cm post then, thanks
Click to expand...
Click to collapse
Oh... lol... I didn't even think of the Uber toolchain... It is a toolchain built by Chet Kener, actually similar to Linaro, I don't know that kernels built with the UberTC are any better than other kernels and the toolchains tries to take key elements of Linaro and SaberMod and combine them... As with any kernel, YMMV, so try them and see what works best for you.
Yes, Marshmallow handles file systems differently, especially when it is portable storage (external storage)... Marshmallow, without root and third party apps, cannot put apps on the SD card, it is just storage space. But the card can be adopted as internal storage, and if you google around, you will see there are ways to split the card into 2 partitions, part of it as internal and part as external storage.
Hi!
Thanks for the info!
I'll try to find any of those third app as I am rooted to move, because the class 10 of my sd card isn't enough and then it's laggy as hell, while I still have 4 gb used in my internal... Like not legit <_<
I already knew that I make partitions on my µsd ^^ But I never tried or so, I will try it soon I guess
Hey there, I am back! Just tried to partition the sd card via TWRP but when I boot the phone after partitionning + swap the phone says that the memory isn't compatible, any help ?
Related
FROYO DESIRE ROMS ARE EXPERIMENTAL, AND MAY NOT BE RELIABLE
http://rapidshare.com/files/396857330/brafrorom6b.zip
This is essentially the same as DeFroST, but with no kernel mods. I'm also testing if SetCPU is really needed any more, with those mods disabled.
v6b
- Fix for a kernel bug, and corrected the driver. Remote key now works.
- Added compiler optimisations.
- (b) fixes broken wireless in 6
v5
Microphone now working in calls.
Credits go to:
Kali- and deovferreira for the kernel source
Paul @Modaco for the base rooted Nexus rom
Richardtrip for some of the config and userspace drivers I pinched from DeFroST
Me... well I'm just the chef ;-)
Working:
- Wifi N & Tethering
- GPS
- BT
- Digital compass
- Proximity sensor
- Optical pad
- Camera
- Keypad
- Headset
- Remotekey
- Touchscreen
- Vibrator
- LED
- many others
- APPS2SD
- SetCPU
- MIC
Not working:
- Ambient light sensor (works, but not calibrated)
- Camcorder (reboots the phone)
- Dock on USB
- Facebook contacts sync
Bug:
- Echo
SetCPU - Battery life
If you are experiencing battery live issues, then you should probably set up SetCPU. There are possibly still issues with the display, as some people are reporting high display battery usage. However, these steps can make a BIG difference.
1. Find SetCPU in your programs.
2. If you are asked to choose a device, choose the bottom item "Custom Frequencies..."
3. You may be asked for root access. You should allow this.
4. Tick "Auto-refresh" and "Set on Boot" and ensure CPI Governor is set to "ondemand"
5. No profiles are needed. I'd say you need a good understanding of how processes and threads work, and what the impact is to do any use here... and if that's you, then you won't be reading this guide.
6. Confirm your settings against the image (attached).
APPS2SD - Install apps on your SD card.
First of all... this is not APPS2SD. It is a new feature build into FroYo. Secondly, yes, it does work... just it hasn't been enabled in many apps yet by the developers (see the background posted below).
Some background
The Android platform now allows applications to request installation onto the device's external storage media (such as the SD card), as an alternative to installation onto the device's internal memory.
Application developers can express the preferred installation location for their applications by means of a new attribute of <manifest> in the manifest file, android:installLocation. The attribute supports three values: "internalOnly", "preferExternal", and "auto". At install time, the system checks the value of android:installLocation and installs the application .apk according to the preferred location, if possible. If the application has requested external installation, the system installs it into a private, encrypted partition in the external media. Once an application .apk is installed externally, the system lets the user change the storage location of the .apk and move it onto the device's internal memory if needed (and vice versa), through Manage Applications in the user settings.
By default, the system installs all applications onto the device's internal memory, except for those that explicitly request external installation. This means that the system will always install legacy applications onto internal memory, since they do not have access to the android:installLocation attribute. However, it is possible to configure and compile a legacy application such that it is installed internally on older versions of the platform and externally on Android 2.2 and later platforms, if necessary.
Note that requesting installation onto the device's external media is not suitable for all applications, particularly because the external media may be removable and unmounting/remounting may disrupt the user experience and system settings.
For more information about setting a preferred install location for your application, including a discussion of what types of applications should and should not request external installation, please read the App Install Location document.
Note: By default, your application will be installed on the internal storage and cannot be installed on the external storage unless the developer defines this attribute to be either "auto" or "preferExternal".
Click to expand...
Click to collapse
Install ALL apps to SD
However, it is possibly to force everything to be installed on external SD. I think this is the ONLY way you can do it, and then you have to move anything back to internal memory (such as widgets) which need to be there.
Using adb.exe (this is part of the android developer kit, but is also part of r5-desire-root (which you used to root your phone), available here: http://android.modaco.com/content/ht...-1-21-support/
adb will be called adb-windows adb-mac or adb-linux, depending on your os.
1. Install the ROM
2. Reboot the phone
3. Open up a cmd/bash prompt, somewhere you have access to adb
4. run: adb-<youros> shell pm setInstallLocation 2
To anyone who types "adb-<youros>"... you shouldn't be here!
This will force all apps to be installed to SD
Other options are:
adb-<youros> shell pm setInstallLocation 0
- This causes apps to be installed to their preferred location. For 99.9% of current apps, this will be internal memory, and it won't be possible to move them.
adb-<youros> shell pm setInstallLocation 1
- This causes ALL apps to be installed to internal memory. For 99.9% of current apps it won't be possible to move them.
MAKE SURE YOU MOVE YOUR WIDGETS TO INTERNAL MEMORY, OR THEY WILL DISAPPEAR
Hi, can you add a mirror please.
Great rom, I was previously using DeFrost, but now with BraFro I have wifi-tether working
I look forward to this, but wont flash it before its proofed good and the release log ofcourse
Noob question: where can i find some information about this rom? Thank you very much for answering
DennisG1 said:
Noob question: where can i find some information about this rom? Thank you very much for answering
Click to expand...
Click to collapse
Release note to follow..
Edit: you can find info in the first post now
DennisG1 said:
Noob question: where can i find some information about this rom? Thank you very much for answering
Click to expand...
Click to collapse
Check the first post now... that enough for ya?
martinlong78 said:
Check the first post now... that enough for ya?
Click to expand...
Click to collapse
Looks good, but could you plz add some screenshots?
And oh, btw.. what is the difference between this and DeFrost?
On paper it looks the same, what have you improved?
Edit: after a better look it seems that you have copypasted the info from DeFrost thread..
This makes me a bit sad.. plz dont say your a saxer (thief)
infexis said:
Looks good, but could you plz add some screenshots?
Click to expand...
Click to collapse
I'm not going to, but somebody might like to post them.
infexis said:
And oh, btw.. what is the difference between this and DeFrost?
On paper it looks the same, what have you improved?
Click to expand...
Click to collapse
It's a completely different approact to DeFrost. This is a new kernel, hacked for the bravo board (desire), whereas richardtrip ported froyo kernel stuff back to the 2.6.29 kernel.
Basically, functionally, you're getting wifi hotspot, but we should hopefully progress further with this kernel.
Flash is in sync
JD
wipe
Is a wipe necessary when changing from DeFroST 0.6 to this?
Thanks,
Dan.
martinlong78 said:
This is a new kernel, hacked for the bravo board (desire)
Basically, functionally, you're getting wifi hotspot, but we should hopefully progress further with this kernel.
Click to expand...
Click to collapse
Since there is a new kernel, i wonder if its faster, more stable, or anything that is reason enough to flash it - running DeFrost 06 right now.
dboy0911 said:
Is a wipe necessary when changing from DeFroST 0.6 to this?
Thanks,
Dan.
Click to expand...
Click to collapse
I didn't wipe when changing from DeFrost 0.6 and everything appears to be OK for me
thanks and sorry for my english
I Have eclair 2.1 original rom 1.15 with root ability.. i have possibility to flash directly this rom? or not? for flash i going to recovery and flash any zip from sd card good?
dboy0911 said:
Is a wipe necessary when changing from DeFroST 0.6 to this?
Thanks,
Dan.
Click to expand...
Click to collapse
Nope. No flash required.
infexis said:
Since there is a new kernel, i wonder if its faster, more stable, or anything that is reason enough to flash it - running DeFrost 06 right now.
Click to expand...
Click to collapse
My understanding (which isn't great!) is that this is a less "hackish" way of getting Froyo to run on the Desire. DeFrost uses the kernel from a standard Desire ROM with the Froyo bits bolted on. This way of doing things actually uses a proper Froyo kernel thats been tweaked to run on the Desire, so should be more stable.
Is there any specific radio version this should be used with?
So the Kernel is the one posted here: http://forum.xda-developers.com/showthread.php?t=696846 ?
2.6.32.9? So WiFi 802.11n should work?
Also i assume it does not have oc/uv? :/
infexis said:
Since there is a new kernel, i wonder if its faster, more stable, or anything that is reason enough to flash it - running DeFrost 06 right now.
Click to expand...
Click to collapse
Have a read of the original kernel thread... read for yourself
http://forum.xda-developers.com/showthread.php?t=696846
martinlong78 said:
Check the first post now... that enough for ya?
Click to expand...
Click to collapse
Wonderfull....thank you
Hello,
I have a HTC Touch Diamond 100 and I installed the "Froyo FRX06 XDandroid NEW system update" review in the post "[prj] [XDANDROID] [AOSP] [FroYo | GINGERBREAD] [31.03] System Update" and everything works fine except that it doesn't recognize SDcard applications.
There's no Error Message in the screen, is just that the system doesn't recognice anything in the SDcard. I put my apps in the folder: AndroidApps-> Other. I think it's not the common fault that I have read many people have "Waiting for SDCard error. For people who have problems with sdcard message, add this to your startupmsmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave" because for instance the phone let me save the pictures i've take with the camera phone or install and recognice any app from the market.
I 've Format the card with the HP tools after initial installation and then i had restore all the files in the internal storage.
P.S. Sorry for my possible spelling mistakes but English is not my native language
Keep in mind if you put the apk in anything other than the AndroidApps folder you will need to install them yourself. See THIS FAQ for further explanation. As far as the wating on sd card message you get when you are booting into Android, I get those all the time and have no problems with taking pictures. I would suggest that you use the full bundle from THIS post to ensure you have the latest. Unless you know what you are doing
R^7Z said:
Keep in mind if you put the apk in anything other than the AndroidApps folder you will need to install them yourself. See THIS FAQ for further explanation. As far as the wating on sd card message you get when you are booting into Android, I get those all the time and have no problems with taking pictures. I would suggest that you use the full bundle from THIS post to ensure you have the latest. Unless you know what you are doing
Click to expand...
Click to collapse
Oh what A noob mistake xD I didn't know that apps in the "Other" folder doesn't follow the "typical rules" for instaling apps (i've come from previous releases of Android, Eclair specifically, and in that version it was only place in this folder to install apps).
I'm using froyo instead of gingerbread builts because HTC touch Diamond it's quite old and i don't know if the performance would be better or slower than froyo performace but if you recomend me to use that gingerbread bundle i would use it.
Thanks R^7Z.
Honestly, Gingerbread is "better" but it is alpha release at the moment. Yes, this means that there are quite a few more "improvements" to under-go! I only recommend it if you like the idea of Android. The latest releases for FroYo aren't bad but it seems there are a few hard instability hits it has taken since FRX03 (last time I really enjoyed running a FroYo build from the XDAndroid project). Since then, I've been playing around with a few things and builds to include but not limited to this new idea of CWM (clockwork mod/Gingercherry tutorial) which is posted in the neopeek forums. So, unless you've got an idea as to how neopeek variants work, it's suggested to stick with the XDAndroid builds...
R^7Z said:
Honestly, Gingerbread is "better" but it is alpha release at the moment. Yes, this means that there are quite a few more "improvements" to under-go! I only recommend it if you like the idea of Android. The latest releases for FroYo aren't bad but it seems there are a few hard instability hits it has taken since FRX03 (last time I really enjoyed running a FroYo build from the XDAndroid project). Since then, I've been playing around with a few things and builds to include but not limited to this new idea of CWM (clockwork mod/Gingercherry tutorial) which is posted in the neopeek forums. So, unless you've got an idea as to how neopeek variants work, it's suggested to stick with the XDAndroid builds...
Click to expand...
Click to collapse
I see what you say but honestly, right now, I'm looking for stability and performace, if you know that gingerbread build GBX0A have better performance (i supose that it's less stable because it's an alpha) than FRX06 i'll choose Ginger
Thanks again R^7Z.
Hi guys, I am new here so try to be gentle.
This was the first time I've ever tried to do something with my phone (Nexus S) from the day I've bought it. (Ver 2.3.4)
I did my homework, and tried to install a new Mod.
I have tried many Roms from the last couple of days, but for some strange reason non of them worked fast enough (at least as my old version).
(well and the fact that it erased my SD card with all the info I've had there...)
The one version that looked ok from first sight was:
CyanogenMod 9 v4.0.3 v3.4 + CM Night builds
Now I'm having lots of different issues, and have no idea if someone already solved them, or should I just return to the working old version I had.
The first thing is -> I cannot move Apps to the SD storage, Under the Storage cattegory i have no option to choose to install apps on the SD (like I had with the old version), and under Apps - the "move to SD card" is Grey.
another thing is the languages, why do I see Chinese and other langauged by default and Im unable to uncheck them?
there are many more issues, but these are the most annoying ones for now.
I cannot reply to the version thread, so who can advice?
Thanks!
There are MANY roms for the Nexus. You just have to try a few and find one to your liking. The Chinese text you were talking about might of been an MIUI rom. They are based from China. When you go through the setup screen on each rom after you flash, make sure you choose the appropriate language to your liking.
On another hand. If you tried an ICS rom, then I think apps to sd don't work on Ice Cream Sandwich. I am not 100% sure, though. Please don't take my word for it.
Some roms might have bugs, some might work 100%. Just do the reading and flashing and learn from experience. Its the best way.
BTW. Welcome to XDA!
Well not quite.
mabry said:
There are MANY roms for the Nexus. You just have to try a few and find one to your liking. The Chinese text you were talking about might of been an MIUI rom. They are based from China. When you go through the setup screen on each rom after you flash, make sure you choose the appropriate language to your liking.
On another hand. If you tried an ICS rom, then I think apps to sd don't work on Ice Cream Sandwich. I am not 100% sure, though. Please don't take my word for it.
Some roms might have bugs, some might work 100%. Just do the reading and flashing and learn from experience. Its the best way.
BTW. Welcome to XDA!
Click to expand...
Click to collapse
The MOD is the most recent CM9 mod, (named in the topic).
I dont see why is it related with the fact I cannot uncheck the unneeded language like Chinese.
but the language part is not much of an issue like the SD card.
I am not trying to run old Apps, since my SD was formatted during the upgrade,
I am trying to move - or choose where to install current apps, ability I had before this Version.
I have an image to attache, but I cannot since I am a new member.
any reason why other mods for the same phone were working very slow? (Clean installation)
thanks for the quick reply.
The ability to move/force all apps to to SD or pick a default install location is not included in the rom yet. Do it manually with a app if you want to move something to SD that doesn't support being moved there.
albundy2010 said:
The ability to move/force all apps to to SD or pick a default install location is not included in the rom yet. Do it manually with a app if you want to move something to SD that doesn't support being moved there.
Click to expand...
Click to collapse
Just tried it, same thing, Apps cannot move to the SDcard.
I find the "Airplane" icon can't be shown on the top when you choose "text" in Signal status style.
ROM: CM9 v3.4
KERNEL: Matr1x v17.5
Onlyktm said:
Just tried it, same thing, Apps cannot move to the SDcard.
Click to expand...
Click to collapse
How did you try it?
I have not used that particular rom myself but have used kangs and am running a official nightly build of cm9.
albundy2010 said:
How did you try it?
I have not used that particular rom myself but have used kangs and am running a official nightly build of cm9.
Click to expand...
Click to collapse
I have d/l couple of apps that move to usb, they all say apps cannot be moved to the SD, those apps (like facebook) were already on my SD with the old version.
Just because the old version allowed to move them to SD that does not mean the apps support it. Again since the feature to do it within the rom itself is not there yet you have to do it manually with a third party app. Titanium backup or one of the who knows how many root apps2sd apps will move it
albundy2010 said:
Just because the old version allowed to move them to SD that does not mean the apps support it. Again since the feature to do it within the rom itself is not there yet you have to do it manually with a third party app. Titanium backup or one of the who knows how many root apps2sd apps will move it
Click to expand...
Click to collapse
Got it, thanks.
another thing, when unlocking the device I have two options.
one is to unlock, and the other one is the camera.
Q: 1. can i switch the camera with something else?
2. I have seen roms with 4 -5 -6 different options to unlock, how can I have this feature?
thanks again.
That is a feature built into that rom. Cyan doesn't have it yet. Not sure what options they are planning to add to lock screen . Just a place holder for now in settings. There are lock screen replacements on the market you could install if you like.
Try CNA or the more stable CM7.2
CM9 made by Kalim doesn't have these features right now. You could try a different ROM called "Codename Android" (CNA) which is based on ICS.
However, all these ROMs are not in their final stage. A better choice to try would be the CyanogenMod 7.2 for NS. I was using it while I was on GB, works wonders, although expect BSOD some times...
Enjoy the testing!
Onlyktm said:
Got it, thanks.
another thing, when unlocking the device I have two options.
one is to unlock, and the other one is the camera.
Q: 1. can i switch the camera with something else?
2. I have seen roms with 4 -5 -6 different options to unlock, how can I have this feature?
thanks again.
Click to expand...
Click to collapse
Hi,
I am new this this whole Samsung Galaxy S3 customization. Yesterday, I took the big risk of getting my phone bricked and successfully rooted my phone. Now, I am interested in installing some interesting ROMs and uninstall some uninteresting bloatware. However, I do not know where and how to start.
Just a quick note. I have followed [GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2 OTA ***UPDATED 3/5*** to customize my phone, using ClockworkMod Touch Recovery 6.0.2.3 and MD5: 8C3DA18BD5DEF7E38E03DD147A0E10A1 for VRBMB1 (Jelly Bean 4.1.2). My phone's Model Number is SCH-I535, Android Version 4.1.2.
The first thing I want to do is to reformat my phone. By that, I mean improving the battery life, speed, and practically everything else related to those two things I just said. I have read somewhere that custom ROMs can improve battery life, as well as make everything in the phone move faster and smoother. A few ROMs have caught my attention, but I am unsure of which ROM to use. I have also noticed that you can change the battery preferences without the need of a ROM, but nevertheless, a custom ROM couldn't hurt. Plus, I really want to change the theme of my phone, specifically replacing them with [OMG][THEME] 03.21 - Ultimate OMG Theme - 35 Choices - Aroma - CleanROM/Stock.
So the first question is, which is the most preferred ROM to use for my phone? (Or better yet, do I even need a custom ROM?) So far, my main goal is to improve the speed and battery life. But I have noticed that you must factory reset your phone. That is a little discouraging as there are many personal things in my phone that I would love to keep. I do have Titanium Backup, however, I am unsure of how to use it. Is there a guide on how to use Titanium Backup? I am also concerned that a factory reset can and will clear everything in Titanium Backup as well. The next thing is, I am using Next Launcher by Go Developers. I really enjoy the launcher and would like to continue using it. Will I still be able to use the launcher in custom ROMs?
Thank you for your help!
Zarotu said:
Hi,
I am new this this whole Samsung Galaxy S3 customization. Yesterday, I took the big risk of getting my phone bricked and successfully rooted my phone. Now, I am interested in installing some interesting ROMs and uninstall some uninteresting bloatware. However, I do not know where and how to start.
Just a quick note. I have followed [GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2 OTA ***UPDATED 3/5*** to customize my phone, using ClockworkMod Touch Recovery 6.0.2.3 and MD5: 8C3DA18BD5DEF7E38E03DD147A0E10A1 for VRBMB1 (Jelly Bean 4.1.2). My phone's Model Number is SCH-I535, Android Version 4.1.2.
The first thing I want to do is to reformat my phone. By that, I mean improving the battery life, speed, and practically everything else related to those two things I just said. I have read somewhere that custom ROMs can improve battery life, as well as make everything in the phone move faster and smoother. A few ROMs have caught my attention, but I am unsure of which ROM to use. I have also noticed that you can change the battery preferences without the need of a ROM, but nevertheless, a custom ROM couldn't hurt. Plus, I really want to change the theme of my phone, specifically replacing them with [OMG][THEME] 03.21 - Ultimate OMG Theme - 35 Choices - Aroma - CleanROM/Stock.
So the first question is, which is the most preferred ROM to use for my phone? (Or better yet, do I even need a custom ROM?) So far, my main goal is to improve the speed and battery life. But I have noticed that you must factory reset your phone. That is a little discouraging as there are many personal things in my phone that I would love to keep. I do have Titanium Backup, however, I am unsure of how to use it. Is there a guide on how to use Titanium Backup? I am also concerned that a factory reset can and will clear everything in Titanium Backup as well. The next thing is, I am using Next Launcher by Go Developers. I really enjoy the launcher and would like to continue using it. Will I still be able to use the launcher in custom ROMs?
Thank you for your help!
Click to expand...
Click to collapse
You don't have to flash a custom ROM to improve battery just a custom kernel. There are a lot of custom tweaks that the developers put in their ROMs to further improve the ROM some you can put yourself. As for the themes the stock ROM has to be deodexed in order for the themes to work. Lastly Next launcher is an app and the last time I checked all launcher apps work on rooted phones.
jmxc23 said:
You don't have to flash a custom ROM to improve battery just a custom kernel. There are a lot of custom tweaks that the developers put in their ROMs to further improve the ROM some you can put yourself. As for the themes the stock ROM has to be deodexed in order for the themes to work. Lastly Next launcher is an app and the last time I checked all launcher apps work on rooted phones.
Click to expand...
Click to collapse
Thank you for the reply. Seeing how it is, where can I find custom kernels and/or a guide on how to install and use a custom kernel on my phone? I do not quite understand what you mean when "the stock ROM has to be deodexed in order for the themes to work." Lets say I am interested in one of those custom theme, does that mean I have to personally deodex the ROMs or can I just follow the instructions stated in the main thread? So far I do not have a custom ROM after rooting my phone. Everything is still the same since I did the last step, which was to flash the Jelly Bean Bootchain.
Edit: Is there a thread I can look at find to get more information on how to prepare my phone for theming and modding? Information such as deodexing my phone, and other preparation information. I can't seem to find a good thread.
Zarotu said:
Thank you for the reply. Seeing how it is, where can I find custom kernels and/or a guide on how to install and use a custom kernel on my phone? I do not quite understand what you mean when "the stock ROM has to be deodexed in order for the themes to work." Lets say I am interested in one of those custom theme, does that mean I have to personally deodex the ROMs or can I just follow the instructions stated in the main thread? So far I do not have a custom ROM after rooting my phone. Everything is still the same since I did the last step, which was to flash the Jelly Bean Bootchain.
Click to expand...
Click to collapse
In the original android development is where you will find the kernels. Most of the kernel threads will provide links and the information you need. If you are planning on flashing KT747 kernel here is some additional information: http://forum.xda-developers.com/showthread.php?t=2144004
Whoa, hold up on the custom kernels and custom rom stuff.
1. You need to make a back up with either twrp or cwm. Next put your important files on your external sd including your efi. Idk if titanium backup allows you to store app back ups on the external sd or not but I assume it does (I use a diff app). You don't have to format your internal sd to flash a custom rom, you have to format the system partition.
Take a minute to make sure you have the prerequisites before moding your phone more. You cannot possibly want to be doing all this so soon especially if you just got into this yesterday.
2. Your still on a stock rom, which is odexed. If you want to customize your rom you need to be on a deodexed rom most of the time. This is a the simple abbreviated difference between odexed and deodexed.
3. Luke took on Vader, even though he was a new rookie padawan. He didnt have a good grip on what he was doing, and karma took his hand and slapped him in the face with irony for it. You might find yourself falling a deep hole of problems if you don't read up more on what you're doing. Do yourself a favor and stay on the god damn dagobah system awhile.
One final thing I have to say is do some research it will help you a lot.
Well, if you want the pure AOSP feel with a CM base, yet uber customization and tweakability I would go with paranoidkangdroid. It mixes CM as a base, with AOKP and ParanoidAndroid. This is what I use and I love it. Cleanrom is a touchwiz rom and I personally feel that while TW roms are stable and usually butter, they are all missing some aspects of customization. Link to the rom: http://forum.xda-developers.com/showthread.php?t=2186838. However that's my opinion. I prefer the clean stock google experience, others may not. Happy flashing
EDIT: before you go flash anything make sure you do the following: (in this order)
1. Root device
2. Unlock the bootloader
3. Install TWRP (or CWM, I like TWRP)
4. Make a backup of the current stock rom
5. Take all the things you want to save (pictures) and back them up to your computer.
6. DO NOT UNDER ANY CIRCUMSTANCES TRY TO INSTALL A ROM MADE FOR THE INTERNATIONAL, AT&T, NOTE2, etc. You will brick your phone. Stick to the Verizon variant thread and you should be fine. If getting the rom from another website, make sure it is made for SCH-I535 or D2VZW.
nrock2256 said:
Well, if you want the pure AOSP feel with a CM base, yet uber customization and tweakability I would go with paranoidkangdroid. It mixes CM as a base, with AOKP and ParanoidAndroid. This is what I use and I love it. Cleanrom is a touchwiz rom and I personally feel that while TW roms are stable and usually butter, they are all missing some aspects of customization. Link to the rom: http://forum.xda-developers.com/showthread.php?t=2186838. However that's my opinion. I prefer the clean stock google experience, others may not. Happy flashing
EDIT: before you go flash anything make sure you do the following: (in this order)
1. Root device
2. Unlock the bootloader
3. Install TWRP (or CWM, I like TWRP)
4. Make a backup of the current stock rom
5. Take all the things you want to save (pictures) and back them up to your computer.
6. DO NOT UNDER ANY CIRCUMSTANCES TRY TO INSTALL A ROM MADE FOR THE INTERNATIONAL, AT&T, NOTE2, etc. You will brick your phone. Stick to the Verizon variant thread and you should be fine. If getting the rom from another website, make sure it is made for SCH-I535 or D2VZW.
Click to expand...
Click to collapse
Ok he is a newbie in this so pretty much AOSP especially those are a little bit advance for him.
jmxc23 said:
Ok he is a newbie in this so pretty much AOSP especially those are a little bit advance for him.
Click to expand...
Click to collapse
Haha! Seeing how there is so much to know before I can get started on anything, I believe I will be needing to do more research. So first thing's first. If all I did was root my phone, using the clockwork recovery mod, what should be my next move? Where do I go from here? I have been searching, but have not yet found a guide. How do I backup my stuff in clockwork recovery mod? What do I do if I do not have an external SD card? Haha, I didn't think customizing your phone would be this difficult.
Thank you.
Zarotu said:
Haha! Seeing how there is so much to know before I can get started on anything, I believe I will be needing to do more research. So first thing's first. If all I did was root my phone, using the clockwork recovery mod, what should be my next move? Where do I go from here? I have been searching, but have not yet found a guide. How do I backup my stuff in clockwork recovery mod? What do I do if I do not have an external SD card? Haha, I didn't think customizing your phone would be this difficult.
Thank you.
Click to expand...
Click to collapse
It is more confusing than it is difficult.
Essentially your next move is preparing yourself incase you fail flashing a rom. You need to do the following:
1. Get a micro sdcard, atleast 16gb
2. Make a back up on the external sd you acquired in step 1 above. This can be done from cwm by selecting "Back up and restore" from the menu, followed by selecting the back up option that says back up to external sd.
3. Now download the rom you want on to your external sd card. Find out if the rom requires gapps or any other supplemental downloads and put them on the external sd as well.
4. Next, report back here for further instructions.
(I havent used cwm for a while so the instructions I gave there are from memory, double check on that)
Surge1223
Surge1223 said:
Essentially your next move is preparing yourself incase you fail flashing a rom. You need to do the following:
1. Get a micro sdcard, atleast 16gb
2. Make a back up on the external sd you acquired in step 1 above. This can be done from cwm by selecting "Back up and restore" from the menu, followed by selecting the back up option that says back up to external sd.
3. Now download the rom you want on to your external sd card. Find out if the rom requires gapps or any other supplemental downloads and put them on the external sd as well.
4. Next, report back here for further instructions.
(I havent used cwm for a while so the instructions I gave there are from memory, double check on that)
Surge1223
Click to expand...
Click to collapse
Okay what if the person doesn't have the money as of now to purchase an sd card? Are there other ways to back up their data?
Sure you can back it up on your internal sd card, but generally you would only do that if you were very familiar with how your recovery works and know exactly what you were doing. Most of the time that means you've had previous experience with the rom your flashing and/or arent too woried about your stuff getting deleted. Usually its a good idea to keep a flashable zip of a deodexed stock rom, radio, recovery, bootchain, etc. In the internal if your doing that but since he's just starting out I wouldn't do that and I usually dont anyways. Its risky and not worth losing your stuff when you could just spend a couple bucks and get a external micro sd.
Surge1223
Surge1223 said:
Sure you can back it up on your internal sd card, but generally you would only do that if you were very familiar with how your recovery works and know exactly what you were doing. Most of the time that means you've had previous experience with the rom your flashing and/or arent too woried about your stuff getting deleted. Usually its a good idea to keep a flashable zip of a deodexed stock rom, radio, recovery, bootchain, etc. In the internal if your doing that but since he's just starting out I wouldn't do that and I usually dont anyways. Its risky and not worth losing your stuff when you could just spend a couple bucks and get a external micro sd.
Surge1223
Click to expand...
Click to collapse
Micro SD price range from $5-$100 retail when not on sale and the retail price depends on the storage size. So if the person is hard on cash or has more important things to spend their money she/he might not be able to buy the micro sd with the couple of bucks that you said it cost. The reason I asked those questions is that not everyone has a couple of dollars to spare on a micro sd card so all possible ways to back up data should be mentioned not just what you or I think is the best thing to do. For instance I have my data backed up on my computer via external hard drive as well as Google drive, box and Dropbox. I also use Carbon instead of the titanium backup app that everyone suggests to use. So they can use their computer, cloud storage service, external hard drive, micro sd cards and apps to backup their data.
Its not a matter of whether its possible or not, I mean yeah you can also make a system image of your pc using DVD's instead of a portable hdd or flash drive. I can understand people may be short on cash, but if you have enough time and money to root your phone, pay for a data plan, subscribe to the internet, you can budget 5 dollars. Hell, you could even start using bing rewards to get yourself a 5$ Amazon credit.
All I am saying mainly is that there are more ways to back up your data besides micro sd cards and that all people new to rooting should know more then one way as something can go wrong your micro sd card so your data should be backed up in other ways to insure that you can restore your data.
I hear ya, I guess I just think because I learned my own how to use other methods I assumed that as people got more familiar with flashing roms, etc, that they'd learn eventually too. But hey to each his own. IMO, the external sd is the easiest, fastest, and most reliable way so in this case, I think we should leave well enough alone.
Surge1223
On my Samsung GT-N7000 I'm trying Omnirom again. I've tried it in the past and also tried vanilla CM stable and nightlies. I have also tried SuperNexus and PA and some other stuff that left no impression. Basically on this device for functional hardware, reasonable user control and a coherent UI it is Samsung's Touchwiz rooted, or Omnirom.
It is a bit too hard to install Omnirom and it can be horribly tedious to go from Omnirom back to stock or to another ROM. It's OK after you have done it a few times, but it is a huge obstacle for anyone trying to discover the way via inaccurate, misleading and fragmented documentation. The install guide at omnirom.org is actually utterly useless for this particular device, a complete non-starter. XpLoDWilD your GT-N7000 specific thread at http://forum.xda-developers.com/showthread.php?t=2516933 almost guarantees a boot loop because it only mentions but doesn't identify or link to versions of CWM which are adequate. In fact unless the user by diligent searching (or more likely by blind chance) comes across a link to the specific suitable raw kernel then it is one big dead end. You could spend hours and days searching for a suitable CWM and never find it because actually you should be searching for raw_kernel_r#_j##.zip. But how is anyone meant to know this. It turns what is actually a reliable and rather trouble free 15 or 20 minute process into a some kind of waking torment. In the past the documentation on installing via CWM was so bad that I used ODIN, which is less than ideal IMO because it means that anyone switching from stock to Omni doesn't get the chance to make a full nandroid backup of the original system (so to revert means a very tedious clean install).
So assuming the end user somehow finds the right raw kernel whose recovery can install Omnirom, what should they do? Of course they should back up their current apps and also make a nandroid backup. Apps backup is easy with oandbackup or titanium or similar. How about a nandroid backup to external SD? No problem in CWM but once you have TWRP installed you can't use it to access anything on an exfat formatted external SD card! You can back up before installing Omnirom but afterwards you can't restore! This is 100% nuts. exfat has now been around for 8 years. CWM supports it brilliantly. Even my crusty old Debian stable desktop reads and writes to exfat at very high speeds even via a FUSE FS and my puny Asus EeePC netbook running XP Home handles it fine. TWRP? Nope. exfat? Wha tha? Aaaaaagh.
Sorry to rant But for these specific devices Omnirom (with an exfat SD) is really the only high quality competitor to the stock Samsung, and there surely isn't a good reason for it being so frustrating to install and also to revert? Is TWRP really such a killer facility that it is worth foregoing the ability to backup and restore to the now very common exfat microSDHC? I run plain CM 11 on another device and OTA updates work fine on that. In these days of phatter pipes is it really worth making a huge compromise in functionality simply to avoid 200MB of downloads sometimes? On this device the delta updates are going to fail for many anyway unless they use an exfat card, but if they use an exfat card they.....oooouuuurrrggg...vicious circle.
/rant over.
Loving Omnirom btw and writing as a fan.
#blamesamsung
The Exynos Galaxy S2 family are some of the only devices remaining that don't have separate recovery partitions. This has always led to various annoyances for custom firmware users since it's impossible to change recovery without changing kernel.
Probably the documentation could be updated to indicate a double-flash though. Flash once to get a working recovery, flash a second time to get a working /system
Entropy512 said:
#blamesamsung
The Exynos Galaxy S2 family are some of the only devices remaining that don't have separate recovery partitions. This has always led to various annoyances for custom firmware users since it's impossible to change recovery without changing kernel.
Probably the documentation could be updated to indicate a double-flash though. Flash once to get a working recovery, flash a second time to get a working /system
Click to expand...
Click to collapse
Thanks for responding. I do appreciate that the exynos based devices are sons-of-b...b...bad persons.
I know documentation is boring and mostly thankless but it also matters a lot, most especially for projects which invite the user to perform realtively complex and potentially hazardous tasks.
Personally I would be very happy to edit/update XpLoDWilD's guide, but of course I can't because it's a forum post, not a wiki, so he owns it and it will remain there guiding new and trusting people into disappointment and boot loop oblivion until he decides to change it.
Omnirom has some issues but on the GT-N7000 is probably the only really mature and coherent alternative UI to Samsung's Touchwiz. To me it seems simply insane to direct newcomers into an unnecessary, time consuming, badly described and potentialy hazardous obstacle course, when in fact installation can be done with only small inconvenience.
I'm currently looking for information about installing OmniROM (I'm currently running CM11 nightlies), and I can attest the information in XpLoDWilD's post is somewhat vague, and also doesn't fully correlate with the directions to install Omni at the official wiki -- I'm assuming this lack of correlation is partly due to the fact, mentioned in this thread, that the N7000 doesn't have a separate recovery partition.
Something which made me especially uncertain about the installation process is the following part:
XpLoDWilD said:
- Make sure you're running a proper working ClockworkMod-Recovery - WITH SELINUX SUPPORT!
Click to expand...
Click to collapse
My understanding is that SeLinux is a feature of the kernel -- not the recovery console -- am I wrong about this? Or should I look for SeLinux in the features of the recovery console as well? (if so, how?)
What I currently do, is run adb, or start a console from the normal operating mode (not recovery mode), run the command:
Code:
getenforce
and confirm the reply is:
Code:
Enforcing
which means I have a kernel with SeLinux. Is that good enough to ensure the requisites for the installation are provided?
I'd appreciate any input about this matter.
julian67 said:
Personally I would be very happy to edit/update XpLoDWilD's guide, but of course I can't because it's a forum post, not a wiki, so he owns it and it will remain there guiding new and trusting people into disappointment and boot loop oblivion until he decides to change it.
Click to expand...
Click to collapse
Cant you add device-specific installation guide at the official wiki?
sagie said:
Cant you add device-specific installation guide at the official wiki?
Click to expand...
Click to collapse
I'm back on rooted Samsung TouchWiz. As things stand I wouldn't encourage any normal end user with a GT-N7000 to try a ROM. Hardware support is poor and unlikely to improve, installation documentation is misleading, backup is difficult, and restoring stock Samsung successfully requires ODIN. Also you stand a real chance of bricking the device. On my B+N Nook HD CM11 nightly is, as far as I can tell, beyond criticism but on these Exynos based devices all the third party ROMs have poor hardware support, poor multimedia support, poor stability and truly terrible battery life (even with no gapps installed). I will keep trying out ROMs occasionally and if the day arrives where the hardware is truly supported I will write a guide and drink a bottle of french fizz, but at the moment I would discourage any regular end user from doing anything to their GT-N7000 except running the newest available official firmware and rooting it if required.
I'm pretty sure I can save my twrp backups to my exfat sdcard.
edit: yup. just touch "internal storage" on the twrp backup page and select your sdcard.
julian67 said:
I'm back on rooted Samsung TouchWiz. As things stand I wouldn't encourage any normal end user with a GT-N7000 to try a ROM. Hardware support is poor and unlikely to improve, installation documentation is misleading, backup is difficult, and restoring stock Samsung successfully requires ODIN. Also you stand a real chance of bricking the device. On my B+N Nook HD CM11 nightly is, as far as I can tell, beyond criticism but on these Exynos based devices all the third party ROMs have poor hardware support, poor multimedia support, poor stability and truly terrible battery life (even with no gapps installed). I will keep trying out ROMs occasionally and if the day arrives where the hardware is truly supported I will write a guide and drink a bottle of french fizz, but at the moment I would discourage any regular end user from doing anything to their GT-N7000 except running the newest available official firmware and rooting it if required.
Click to expand...
Click to collapse
i've been using omnirom as my daily driver for 2 weeks now. love kitkat and omnirom features, but its still very unstable i think. stuff that's bothering me for now:
-stock camera is really plain, can't even switch to front camera
-video playback sometimes fail
-music playback will fail the first time i launch and play a song or 2. have to reboot and it'll work all day long
-intermittent random reboots, about 3 times so far the whole week
-wifi signal range is somewhat lower compared to touchwiz rom
-stock clock app, can't manually input time via keypad when you want to add an alarm
-contacts app is very confusing, can't even add a contact with ease. well at least for me that is
other than that kit kat is sure a welcome on this legendary device. contemplating the switch back to stock touchwiz, but loathe at the idea of setting up everything again zzz
In answer to this, and if it can help.
That the second time I install a ROM on my N7000, so it was still a bit frightening for me
Based on a CM10.1, I already had an old CWM.
1) From CWM I've just installed Philz Touch
2) On Philz, i've wiped everything, formated both internal and external sd cards (well I wanted something reeeally clean)
3) Used abd for copying omnirom and Gapp zip on the root
4) installed them from Philz Touch.
And it works like a charm (... but not enough feedback yet, just 2 days).
Now the question is to know if a day Omnirom will accept CWM based recoveries for updates.
TWRP is unfortunately not available on N7000 (from what I see, only USA flavors of Galaxy Note1).
Thanks!
Polux
Polux44 said:
In answer to this, and if it can help.
That the second time I install a ROM on my N7000, so it was still a bit frightening for me
Based on a CM10.1, I already had an old CWM.
1) From CWM I've just installed Philz Touch
2) On Philz, i've wiped everything, formated both internal and external sd cards (well I wanted something reeeally clean)
3) Used abd for copying omnirom and Gapp zip on the root
4) installed them from Philz Touch.
And it works like a charm (... but not enough feedback yet, just 2 days).
Now the question is to know if a day Omnirom will accept CWM based recoveries for updates.
TWRP is unfortunately not available on N7000 (from what I see, only USA flavors of Galaxy Note1).
Thanks!
Polux
Click to expand...
Click to collapse
Per my earlier post - You cannot change kernels on the Samsung GS2 family (including N7000) without also changing recovery.
Conversely, you can't change recovery without changing kernel. It's a limitation of this device since the recovery partition is not actually used, and recovery is in the normal kernel.
Once you flash Omni, your recovery will be TWRP. The reason TWRP doesn't "officially" support any of the GS2 family is because, as I said - you can't change recoveries without changing kernels.
Entropy512 said:
Once you flash Omni, your recovery will be TWRP. The reason TWRP doesn't "officially" support any of the GS2 family is because, as I said - you can't change recoveries without changing kernels.
Click to expand...
Click to collapse
Yes thanks for the precision, i've just seen that now my recovery was TWRP. (well which is good for me since it means I can use OTA). Your details helped me to understand why recovery and kernel are linked together, for my device.
Does it mean that installing omni on a non GS2 device (let's say a more recent device) will not overwrite the existing recovery?
Thanks again!
Polux44 said:
Yes thanks for the precision, i've just seen that now my recovery was TWRP. (well which is good for me since it means I can use OTA). Your details helped me to understand why recovery and kernel are linked together, for my device.
Does it mean that installing omni on a non GS2 device (let's say a more recent device) will not overwrite the existing recovery?
Thanks again!
Click to expand...
Click to collapse
Correct. Sony devices also have this limitation, there is a semi-workaround (where the kernel pulls recovery ramdisk from another location) on those that *in theory* could be done on the old Samsungs... but so few people are working on the old Samsungs that it isn't likely to happen.
Pretty much all GS1s and Exynos GS2s had this limitation. Qualcomm GS2s (Skyrocket/Hercules) had a separate recovery, as did all GS3s and onwards.