Database Users

[APP] Milestone - Overclock (requires root)

Hi all,
I realize this is a post about a Motorola phone but please bear with me.
As you might know, the Milestone firmware is firmly locked, unlike its cousin Droid. Among many things, this forbids overclocking because we can't change the kernel and unlock new frequencies.
However I developed a solution that allows overclocking by changing key structures directly in the kernel memory in runtime. All you need is a rooted phone; no flashing involved. For this to work, the module must know two memory addresses that are specific to each kernel. Fortunately, Motorola appears to have reused its kernel on most 2.1 firmwares, and I've yet to come across a firmware where it doesn't work by default. Confirmed working are Central Europe, Telus and Brazilian firmwares. Testers are welcome to give it a try.
Now for the relevant part for XDA: in theory this can be applied to any kernel on any other phone. You may say it's unneeded because you can already overclock; but you must flash a specific kernel to get a particular speed. It would be much better to be able to set any maximum frequency/voltage on the fly without flashing or rebooting. For instance, you could overclock to 1.0 GHz before a browsing or gaming session and then return to a lower frequency like 600 MHz, though still overcloked, for battery savings and safety. It's up to you.
Milestone users can try it out now:
http://code.google.com/p/milestone-overclock/
For the rest of you, what do you think?

sounds fantastic, I'd love to check it out but for the life of me I can't find the page.
If you want to pm it to me, I'll post it.

Nice. Telus Milestone User here. Would love to learn how to do this for mine.
Here is the project link:
http://code.google.com/p/milestone-overclock/

found it. looks like a fantastic idea.
How can we help get the addresses?

awesome .....wht there is no milestone/droid section here is beyond me ....wtf

Because it was decreed months ago by someone and no one seems to like changing their mind once they make a decision in this day and age.....

but it's need to root, could you fix it？

stevecai said:
but it's need to root, could you fix it？
Click to expand...
Click to collapse
what's the problem with rooting the milestone? There's plenty of solutions for that. Just no custom kernel/ramdisk, which this works around by using a kernel module.

hi,
i use the 2.1-reu version on my milestone,
but in order to prevent the 2.1 introduced alarm bug,
i have updated the kernel (only) to the 2.1-telus
(via a sbf).
is possible to use this mod to overlock my phone?
how?
if not, how help you to obtain the addresses?
thank's and continue your great work!
robert

gemini002 said:
awesome .....wht there is no milestone/droid section here is beyond me ....wtf
Click to expand...
Click to collapse
XDA is a HTC developer forum, not an Android forum. Google some moto modding sites, i know modmymoto.com is pretty good, found out how to root the Cliq (garbage) there.

staticshadow said:
XDA is a HTC developer forum, not an Android forum. Google some moto modding sites, i know modmymoto.com is pretty good, found out how to root the Cliq (garbage) there.
Click to expand...
Click to collapse
I have read this explanation several times.
I do not mind, but then because there are subforums dedicated to sonyericsson, hp, etc in xda.
modmymoto is good but the best developers site is, withous any doubt, xda-developers!

Re: milestone-overclock
Xda-developers is for htc and android is for porn.
Welcome to xda btw and great job. Now prepared to be flamed for uttering the M word.
-------------------------------------
sent via xda app from my milestone

ady said:
android is for porn.
Click to expand...
Click to collapse
are you Steve Jobs ?

miragu said:
Hi all,
Now for the relevant part for XDA: in theory this can be applied to any kernel on any other phone.
Click to expand...
Click to collapse
Will the method to find the right address that will be posted at /wiki/Disassembly work with every phone and kernel,too?
Has the app something like a setting where you can just change the address to the one you found with the method above?
Would really love an overclocked 2.1 on the HTC HERO. There is no oc-2.1-kernel for the Hero, yet.
Thanks for the great work, til now!

this is a good via to mod any application.
please, publish the source code of your applicacion ASAP.
thx

Source code for the kernel module released
Hi all,
Thank you for your support. I've just uploaded the source code for the kernel module and also the standalone module itself (it's included in the apk but still). Will write the Disassembly section soon, stay tuned.

miragu said:
Hi all,
Thank you for your support. I've just uploaded the source code for the kernel module and also the standalone module itself (it's included in the apk but still). Will write the Disassembly section soon, stay tuned.
Click to expand...
Click to collapse
hi,
i'm interested on include this in my system applications directory,
in order to prevent your deletion on hardreset, and in order to make it available FOREVER
the instructions are that:
cp OverClock.apk /system/app
cp OverClock.ko /system/lib
????
thx

The overclock.ko is created automatically when you press the "Load module" button in /data/data/pt.com.darksun.milestoneoverclock/files/overclock.ko. You don't need to copy it. I'm providing it separately so that people can load/bundle it without ever running the apk.
bartito said:
hi,
i'm interested on include this in my system applications directory,
in order to prevent your deletion on hardreset, and in order to make it available FOREVER
the instructions are that:
cp OverClock.apk /system/app
cp OverClock.ko /system/lib
????
thx
Click to expand...
Click to collapse

ok,
if i'm interested on have overclocking on my milestone after boot the system, and don't interested on manually execute the apk on each reboot, i need only to copy the OverClock.ko to /data/data/pt.com.darksun.milestoneoverclock/files/overclock.ko on boot time ?
but in your wiki page says to execute "insmod overclock.ko max_rate=800000 max_vsel=62"
please, provide me instructions to set overclock in boot time

The module created by the apk is preserved across reboots. However, if you want to run the module completely standalone I recommend you put it in /data/local/overclock.ko and run insmod /data/local/overclock.ko max_rate=800000 max_vsel=62

dev activity

this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull

demonoid phenomenom said:
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
Click to expand...
Click to collapse
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.

jeah thats right, i was wondering because my expirience with atrix 2 , previous to the ics update, i was using supercharger rom series, but again i understand that they got a leak to work on, and a bootstrap to flash the restores they where creating, and that stock leaked rom was awesome
sent from the gray stuff inside my skull

mattlgroff said:
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
Click to expand...
Click to collapse
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?

Le_Poilu said:
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Click to expand...
Click to collapse
Would be nice to know for sure. The current methods cannot find 'Android Magic'.

I'm looking forward to seeing this forum get some custom ROMs too...

Looks like progress is getting on with it now

Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.

tiberiu24 said:
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
Click to expand...
Click to collapse
You won't be able to build a full android system from that source. The most you can do is
Code:
$ . build/envsetup.sh
$ lunch generic_x86-eng
$ make [I]target[/I]
Where target is something like out/target/product/generic/system/bin/bluetoothd or bluetoothd

I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Sent from my GT-I9300 using xda app-developers app

hiemanshu said:
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Click to expand...
Click to collapse
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either

turl1 said:
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
Click to expand...
Click to collapse
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H

hiemanshu said:
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
Click to expand...
Click to collapse
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom

turl1 said:
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
Click to expand...
Click to collapse
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me

hiemanshu said:
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
Click to expand...
Click to collapse
Let's continue talking on PM then
re. 2, I actually did need to patch build on AOSP after all . CM on the other hand, has BOARD_CUSTOM_BOOTIMG_MK from the tf tablets.

Hey I posted a rom over at droidrzr.com for use till aosp is ready. This should be enough till we get a jb leak
Sent from my XT890 using Tapatalk 2

Hi Folks
While I don't own a RAZR I , I have been Jaffing around with building CM10.1 and AOSP for x86, I've been getting in going on my FX8120, just need to sort the OpenGLES MESA drivers out.
Anyways I've got CM10.1 built for x86 using the mr1-staging branch ( I think it's been merged to cm10.1 ) and an edited mini-x86 device tree .
Busybox was a B**stard to build though, although on one of the branches there is an .config-minimal-x86 .config-full-x86, still needed tweaking tho.
I submitted my patches http://review.cyanogenmod.org/#/c/27377/ and http://review.cyanogenmod.org/#/c/27373/, however It seems x86 isn't top of cm's agenda.... or I'm missing something about assigning reviewers.
Obviously a base x86 build is only part of the story for you guys as you'll face all the regular problems that emedded devices have, not checked the specs for the RazR but I'm sure there's some binary blobs in your future,
Hack On Folks! :good:

[Q] Help with PA, Matr1x, and my Nexus 4

Hi everyone ,
I got my Nexus 4 yesterday and I love it! Before I got the phone I did a bunch of research on loading custom ROM's and kernels, and even pre downloaded everything so when it arrived I could start tinkering right away. At the moment it seems Paranoid Android is an ideal ROM for me, as it strikes a nice balance between simplicity and customization. However, it seems that the Matr1x kernel doesn't run well on it due to the JSS/JWR incompatibility issue that came about with Android 4.3. I'd like to run the Matr1x kernel because it has a great balance between performance and battery life, and does some fancy GPU over clocking/CPU undervolting for you that I am too afraid to do on my own.
I found a zip file on the xda forums that remedies the incompatibility issue and allows Matr1x v11 and PA 3.99.1 to run together without issue. So my questions are these:
1. Is there any risk in using this JWR/JSS zip patch? Finding it was a pain in the butt and not many people have commented on its quality or where it comes from. Is it safe?
2. PA's gapps package has a bunch of G+ stuff included that I don't care about. Is there a way to remove it like in some of the slim gapps packages?
3. Has anyone else encountered a static hiss/ticking coming from their earpiece? It can only be heard faintly when the device is up to my ear but it's a little frustrating all the same. Is there a fix for this? Does the device's warranty cover it?
4. Finally, I have one thing I am confused about regarding rooting etc: I have CWMod installed on my phone and I have unlocked my bootloader. By unlocking my bootloader, have I also rooted my phone?
Thanks so much for your time!

Downloaded7 said:
Hi everyone ,
I got my Nexus 4 yesterday and I love it! Before I got the phone I did a bunch of research on loading custom ROM's and kernels, and even pre downloaded everything so when it arrived I could start tinkering right away. At the moment it seems Paranoid Android is an ideal ROM for me, as it strikes a nice balance between simplicity and customization. However, it seems that the Matr1x kernel doesn't run well on it due to the JSS/JWR incompatibility issue that came about with Android 4.3. I'd like to run the Matr1x kernel because it has a great balance between performance and battery life, and does some fancy GPU over clocking/CPU undervolting for you that I am too afraid to do on my own.
I found a zip file on the xda forums that remedies the incompatibility issue and allows Matr1x v11 and PA 3.99.1 to run together without issue. So my questions are these:
1. Is there any risk in using this JWR/JSS zip patch? Finding it was a pain in the butt and not many people have commented on its quality or where it comes from. Is it safe?
2. PA's gapps package has a bunch of G+ stuff included that I don't care about. Is there a way to remove it like in some of the slim gapps packages?
3. Has anyone else encountered a static hiss/ticking coming from their earpiece? It can only be heard faintly when the device is up to my ear but it's a little frustrating all the same. Is there a fix for this? Does the device's warranty cover it?
4. Finally, I have one thing I am confused about regarding rooting etc: I have CWMod installed on my phone and I have unlocked my bootloader. By unlocking my bootloader, have I also rooted my phone?
Thanks so much for your time!
Click to expand...
Click to collapse
1. Should be safe, as long as you have a nandroid backup in case something goes wrong.
2. You just delete the apks from the gapps zip. (system/app)
3. Haven't heard of it. Hope someone else has a solution.
4. Well, no. The term "Rooted" only applies to ROMs, when you have a superuser app and binary installed (Supersu, superuser etc.). But, you are just one step from rooting (Flashing the supersu zip).
All custom ROMs are already rooted, so you don't worry about that.

abaaaabbbb63 said:
1. Should be safe, as long as you have a nandroid backup in case something goes wrong.
2. You just delete the apks from the gapps zip. (system/app)
3. Haven't heard of it. Hope someone else has a solution.
4. Well, no. The term "Rooted" only applies to ROMs, when you have a superuser app and binary installed (Supersu, superuser etc.). But, you are just one step from rooting (Flashing the supersu zip).
All custom ROMs are already rooted, so you don't worry about that.
Click to expand...
Click to collapse
Gotcha, thanks very much for the help. So there's no threat of some 12 year old stealing my credit card if I use that JWR/JSS patch zip?

Downloaded7 said:
Gotcha, thanks very much for the help. So there's no threat of some 12 year old stealing my credit card if I use that JWR/JSS patch zip?
Click to expand...
Click to collapse
Most probably not. Certainly not a 12 year old
Give me a link to the zip. I want to check it out a bit.

abaaaabbbb63 said:
Most probably not. Certainly not a 12 year old
Give me a link to the zip. I want to check it out a bit.
Click to expand...
Click to collapse
This is the only thread I could find with a direct link to the .zip, which has me a bit skeptical since downloading it from a Google Drive account seems kind of sketchy.
http://forum.xda-developers.com/showthread.php?p=45690500
That said, it does work. It got PA and Matr1x running together very smoothly, but I reverted to my backup of stock PA before entering any private info because I wanted to see what others had to say about it first.
Thanks again!

Downloaded7 said:
This is the only thread I could find with a direct link to the .zip, which has me a bit skeptical since downloading it from a Google Drive account seems kind of sketchy.
http://forum.xda-developers.com/showthread.php?p=45690500
That said, it does work. It got PA and Matr1x running together very smoothly, but I reverted to my backup of stock PA before entering any private info because I wanted to see what others had to say about it first.
Thanks again!
Click to expand...
Click to collapse
I think it may not work. It has Adreno 200 and MSM8960 libs in it, a GPU and CPU that have nothing to do with the N4's APQ8064 and Adreno 320. You can still try, because they most certainly don't do any "stealing credit card" stuff.

abaaaabbbb63 said:
I think it may not work. It has Adreno 200 and MSM8960 libs in it, a GPU and CPU that have nothing to do with the N4's APQ8064 and Adreno 320. You can still try, because they most certainly don't do any "stealing credit card" stuff.
Click to expand...
Click to collapse
I did some more digging and found that the guy responsible for the patch has a profile on xda, found here: http://forum.xda-developers.com/member.php?u=3873953 and he seems pretty legit. The patch is also linked in the Purified Kernel thread page: http://forum.xda-developers.com/showthread.php?t=2368548 as a recommended work-around for the JSS/JWR graphical glitching. I installed v1.0 on my Nexus 4, which did nothing to help, then I installed v1.2 (linked in OP), and I now have Paranoid Android 3.99.1-RC running (so far) flawlessly on Matr1x v11. Pretty happy about that .

Downloaded7 said:
I did some more digging and found that the guy responsible for the patch has a profile on xda, found here: http://forum.xda-developers.com/member.php?u=3873953 and he seems pretty legit. The patch is also linked in the Purified Kernel thread page: http://forum.xda-developers.com/showthread.php?t=2368548 as a recommended work-around for the JSS/JWR graphical glitching. I installed v1.0 on my Nexus 4, which did nothing to help, then I installed v1.2 (linked in OP), and I now have Paranoid Android 3.99.1-RC running (so far) flawlessly on Matr1x v11. Pretty happy about that .
Click to expand...
Click to collapse
Nice! Good to know.

Paranoid Installer Like CyanogenMod

Yesterday i saw CyanogenMod Installer app for android...
It is quite helpful for those who are flashing roms first time on their device after rooting...
This app also tells them whether a Cyanogen rom is available for their device or not...
I m currently working on paranoid if this feature is added to PA source itself then it will cause pain for other roms...
This will be a arsenal for paranoidsss...
Have a look at CM installer
https://play.google.com/store/apps/details?id=org.cyanogenmod.oneclick
I m not promoting CM but giving u all idea atleast...

It won't cause pain for other roms. People are not exactly lined up waiting for an installer for PA before they can flash it. Not to mention CM devs are quite open to using roms other than CM after using their installer. Its about more than just flashing your favorite rom. its about having a choice other than what your carrier forces you into. And since devs often borrow features from other ROMs, this would hardly be pain for other roms. As tools make developement easier, i think we will see more roms or at least modified roms that have peoples own touch added to them.

Installer will be great for newbies...
theroadrunner said:
It won't cause pain for other roms. People are not exactly lined up waiting for an installer for PA before they can flash it. Not to mention CM devs are quite open to using roms other than CM after using their installer. Its about more than just flashing your favorite rom. its about having a choice other than what your carrier forces you into. And since devs often borrow features from other ROMs, this would hardly be pain for other roms. As tools make developement easier, i think we will see more roms or at least modified roms that have peoples own touch added to them.
Click to expand...
Click to collapse
if a rom offers an installer app then it will attract new users who havent flashed custom roms yet...this what i meant..

Custom ROM Installer
I think that an Automatic Installer for the first flashers would be indeed "comforting" Because I've started to flash custom roms recently and my first one was a pain, not because of the steps....The steps for installing the recovery tool and all are pretty easy and all. But we have the feeling we are going to brick the device at the first flash! hehe Maybe an automatic installer that detects your device model would be kinda safe for unexperienced users...
But nowadays I find it nice to manually flash roms, keep backups, etc...
Oh well...not a bad idea at all in my opinion ;}

That CM Installer is stupid. I used and thought when it said, it will delete your things. I processed that as the normal factory reset in TWRP for a clean flash. Apparently it was a full freaking wipe. Lost everything. I think that process they used it unnessesary.

moneyolo said:
That CM Installer is stupid. I used and thought when it said, it will delete your things. I processed that as the normal factory reset in TWRP for a clean flash. Apparently it was a full freaking wipe. Lost everything. I think that process they used it unnessesary.
Click to expand...
Click to collapse
I don't understand why they needed to wipe the SD card, but you should have read the instructions and backed up your data before installing...

Just as an FYI, the still-in-progress Omni installer is going to be designed such that it can be used by any project. (And cooperation with other projects for inputs is welcome!)
I'm not working on it myself, it's xplodwild's baby - but as an example, there's serious consideration of hooking it into XDA's devdb, although I think it'll require some dependencies metadata to be added to devdb for it to work. (e.g. automagically handle gapps).

stephendt0 said:
I don't understand why they needed to wipe the SD card, but you should have read the instructions and backed up your data before installing...
Click to expand...
Click to collapse
Yeah, that was my fault aswell.

Now it will help..
Entropy512 said:
Just as an FYI, the still-in-progress Omni installer is going to be designed such that it can be used by any project. (And cooperation with other projects for inputs is welcome!)
I'm not working on it myself, it's xplodwild's baby - but as an example, there's serious consideration of hooking it into XDA's devdb, although I think it'll require some dependencies metadata to be added to devdb for it to work. (e.g. automagically handle gapps).
Click to expand...
Click to collapse
Now CyanogenMod team made their Installer Open to all https://github.com/cyngn/OneClickAndroid
this will surely give ideas to other rom developers how to do it in a better way... thnxxx to CyanogenMod

anurag.dev1512 said:
Now CyanogenMod team made their Installer Open to all https://github.com/cyngn/OneClickAndroid
this will surely give ideas to other rom developers how to do it in a better way... thnxxx to CyanogenMod
Click to expand...
Click to collapse
FYI, don't go thanking CM just yet....that source they shared is just for the app which all it does is enable USB debugging hahaha
Is not the source for the installer which I believe is a msi or exe

wait i will check ...
Mazda said:
FYI, don't go thanking CM just yet....that source they shared is just for the app which all it does is enable USB debugging hahaha
Is not the source for the installer which I believe is a msi or exe
Click to expand...
Click to collapse
thnxxx for notifying me... i havent checked the source but i will check now...

nice!

Custom ROM options for SM-T377W

Hello fellow XDA users,
My niece's low end Samsung tablet is extremely slow, even after factory resetting the device.
I used to own one of these devices two years ago, but unfortunately the developer of the old custom rom is no longer able to supply the files or anything to do with the custom rom.
What options do I have for this?
Any help is welcome,
Thank you for reading this!

There's saboorROM, which is the one you're talking about, but its not available as you said.
Lineage OS 15.1 is also available for the t377p, but its in beta and most people are reporting bugs for it, so i wouldnt recommend that, alas, you have no other option so here it is:
[UNOFFICIAL][ROM] LineageOS/Go 15.1 for Galaxy Tab E [SM-T377P/SM-T560NU]
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project...
forum.xda-developers.com

Here's TWRP:
[RECOVERY][TWRP]Samsung Tab E - sm-t560/sm-t561/sm-t560nu/sm-t377p - Update 13/4/2016
Unofficial release -TWRP recovery for the TAB E, both Qualcom and Spreadtrum models Update: TWRP now version 3.0.2-1 https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html...
forum.xda-developers.com
Flash at your own risk, and make sure to take a twrp backup. I wouldnt recommend flashing the lineage rom tho.. I'd recommend rooting your device and optimising it.

PhotonIce said:
There's saboorROM, which is the one you're talking about, but its not available as you said.
Lineage OS 15.1 is also available for the t377p, but its in beta and most people are reporting bugs for it, so i wouldnt recommend that, alas, you have no other option so here it is:
[UNOFFICIAL][ROM] LineageOS/Go 15.1 for Galaxy Tab E [SM-T377P/SM-T560NU]
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project...
forum.xda-developers.com
Click to expand...
Click to collapse
You don't happen to have a copy of SaboorROM do you? The owner no longer does
Thanks for the help btw

no, sadly i dont. maybe try making a new thread and asking in anyone has it. even if they have it installed to their device, they could pull it via a twrp backup and send it to you.

Hey, I just happened to stumble across this thread. I installed saboor rom on my tab sm-t337w quite a while ago and happen to still have the zip file. what would be the best way to share it?

stantheandroidman said:
Hey, I just happened to stumble across this thread. I installed saboor rom on my tab sm-t337w quite a while ago and happen to still have the zip file. what would be the best way to share it?
Click to expand...
Click to collapse
Any online cloud service, such as mediafire, mega, google drive etc.

PhotonIce said:
Any online cloud service, such as mediafire, mega, google drive etc.
Click to expand...
Click to collapse
https://drive.google.com/file/d/1konPZEOAj7WlCBbkGX-iW8UuIVyaySwf/view?usp=sharing
here you go saboor rom for tab E.

Unfortuantely OP was last seen Feb 17th.. don't think he checks xda anymore..

PhotonIce said:
Here's TWRP:
[RECOVERY][TWRP]Samsung Tab E - sm-t560/sm-t561/sm-t560nu/sm-t377p - Update 13/4/2016
Unofficial release -TWRP recovery for the TAB E, both Qualcom and Spreadtrum models Update: TWRP now version 3.0.2-1 https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html...
forum.xda-developers.com
Flash at your own risk, and make sure to take a twrp backup. I wouldnt recommend flashing the lineage rom tho.. I'd recommend rooting your device and optimising it.
Click to expand...
Click to collapse
Hello, a question from a tab e t377V model. I am not familiar with android tablets, and have messed with some custom roms for androids long ago.
If my function with the tab doesn't extend beyond video, reading, and occasional web surfing- I would think optimising it is indeed best, as long as it will be much faster than what I have right now. Sorry to mention it, but just having it be as responsive as my ipad will be fine. Is there any steps videos avialable to do what you mentioned properly? Thank you!

gomavs123 said:
Hello, a question from a tab e t377V model. I am not familiar with android tablets, and have messed with some custom roms for androids long ago.
If my function with the tab doesn't extend beyond video, reading, and occasional web surfing- I would think optimising it is indeed best, as long as it will be much faster than what I have right now. Sorry to mention it, but just having it be as responsive as my ipad will be fine. Is there any steps videos avialable to do what you mentioned properly? Thank you!
Click to expand...
Click to collapse
optimising it is mainly just removing bloatware, and also possibly a kernel manager to boost performance.

PhotonIce said:
optimising it is mainly just removing bloatware, and also possibly a kernel manager to boost performance.
Click to expand...
Click to collapse
Sounds good. Can you link or let me know where I can find the steps to do this? Thank you.

look for a debloat guide. You can do it via adb, but I'm not sure if you'll be able to find a guide for your device. Anywho, just install a root uninstaller app from the playstore and remove extra bloat (be careful though, as you could accidentally brick your device, take a twrp backup before messing with anything). For the kernel manager, I use smartpack kernel manager from the play store, I've also used performance tweaker and it seems to be alright as well.

PhotonIce said:
look for a debloat guide. You can do it via adb, but I'm not sure if you'll be able to find a guide for your device. Anywho, just install a root uninstaller app from the playstore and remove extra bloat (be careful though, as you could accidentally brick your device, take a twrp backup before messing with anything). For the kernel manager, I use smartpack kernel manager from the play store, I've also used performance tweaker and it seems to be alright as well.
Click to expand...
Click to collapse
Er did some searching around, and as you mentioned, there isn't a clear guide for this tablet. If it is not available for this one, can you refer me to a general debloat guide that might be "the best fit" for the tab e? thanks for your continued help.

gomavs123 said:
Er did some searching around, and as you mentioned, there isn't a clear guide for this tablet. If it is not available for this one, can you refer me to a general debloat guide that might be "the best fit" for the tab e? thanks for your continued help.
Click to expand...
Click to collapse
PhotonIce said:
Anywho, just install a root uninstaller app from the playstore and remove extra bloatware (be careful though, as you could accidentally brick your device, take a twrp backup before messing with anything). For the kernel manager, I use smartpack kernel manager from the play store, I've also used performance tweaker and it seems to be alright as well.
Click to expand...
Click to collapse