Dear ROM Devs,
I just wanna throw this out here before rooting season is open: PLEASE PLEASE PLEASE USE SUBVERSION! I kindly ask you all to host/mirror your ROMs on a SVN friendly site such as Google Code for the express fact that it sucks redownloading (and reuploading im sure) ~500mb file because of something like "Changelog: Made a buttload of tweaks that will make your phone be able to run Battlefield 3 on ultra at 60fps AND it will end world hunger AND solve the oil crisis AND if you die it will give you a 1UP!!! (Video proof on first and last! Middle two, just watch the news later!)
Total size of changes: not even 2mb
New ROM Size: still over 500mbI know it sounds like Im whining about nothing, especially those of you with your T1 lines or 50mbps broadband that can download a The Avengers Blu Ray rip, both seasons of MLP: FiM @1080p, and Battlefield 3 (since you thought the video proof was faked and want to test it for yourself) all at the same time and at the speed it would take to toast a poptart with a blowtorch. But it would be a godsend for people who have slow/unreliable internet or only have their data plan and especially for those who are deployed and still trying to feed their flashaholism (such as me) where it literally takes atleast 5-7 days to download a 100mb file with the fastest sustained speed being ~6kb/s, with a ~1 hr downtime every 3-4 hours, not to mention constantly dropping the connection even with a download manager. And also you could set up an automatic commit to upload any changes every night or week or whenever AND instead of having to check the thread every however long, all you would have to do is right click the folder, click SVN update, ???, profit! (LOLZ)
So anyway, theres my argument please consider it. Thanks.
TL;DR: Please host your ROMs on a SVN site so people with slow/unreliable internet connections can download them faster and plus its easier for Devs and flashaholics to keep updated. Thanks.
I don't have this problem but I do hate waiting x amount of time to reflash everything not sure of this method you posted never did it before that I know of but it sounds awesome
Sent from my PG86100 using xda premium
There was a guide for it posted awhile back
http://www.xda-developers.com/android/how-to-use-svn-a-comprehensive-guide/
ckoadiyn: it takes literally 5 steps to set up and 3 to update
1- download and install tortisesvn
2- right click and click checkout where you want it to download to (ie desktop)
3- enter the url to the trunk
4- press ok and let it download
5- zip it up and flash it
to update,
1- right click on the folder and click update
2- wait for it to update if necessary
3- zip it and flash it if it updated
edit: i think you misunderstood, it doesnt make an update folder with only the changes, it updates the whole project folder, which i think is better because there might be some unforeseen problem with only flashing parts instead of the whole thing or something, idk. its still better to download 5mb of updates then wait for the whole thing to flash than to download another 500mb for a 5mb update if you still have to flash the whole thing either way.
the only way you could make it a "changed only update" is if you picked out what was updated but that would probably be more trouble than what its worth and like i said might result in some kind of issue.
xHausx: the problem isnt using svn, its getting those who arnt on it to be on it such as eternity infected 3.5, newts one s, and others
That sounds awesome
Sent from my PG86100 using xda premium
If you have eclipse installed you can also use that, but for a ROM it's probably a lot simpler to just use tortisesvn
I'm feeling stupid now. I have no idea what TLDRBsi or what trunk is (I'm guessing base directory?)
What is wrong with goo.inside etc? Unless I'm misunderstanding the entire point of this thread.
sent from 2yr old Evo on ICS
its ok it stands for too long didnt read lol
and yes the trunk is the base directory, the "/" placeholder of the rom if you will so you dont have to download data, system, sdcard, etc by themselves and to keep them in one place (ie x:/trunk/system/, data/, sdcard/, etc)
goo is fine except for the problems plaguing people like me: slow, unreliable, constant connection dropping internet, not to mention limited bandwidth
i could deal with waiting slowly and patiently but if (when) the connection gets interrupted or dropped then the file is useless and im back to square one minus the amount i downloaded from my allotted bandwidth (do the math too, even if my connection would stay perfectly reliable but just slow: [6kb/s] / 500mb = 23h 40m = OMFGWTF)
and of course jdownloader doesnt work on goo, devhost, androidfilehost, and others (100% offline, file not found) im guessing because theres not plugin to handle the countdown or something
basically my logic is this: dl rom: 500mb, dl updates: 1/5/10+mb at a time > dl rom: 500mb, dl updates 500mb again
see what im getting at?
Wait Sense roms are 500 MB or more now days?
the one in particular im referencing is "newts one s" w/ ics 4.0.3 + sense 4, 508.83mb
and that number is sure to climb when downloading for newer devices like the one series/evo lte
yes there are the cm9's and such that are less than 200 or even 150 but the problem still stands with the connection interrupt/drop = waste of time and bandwidth and having to start over
maybe im reading to much into it.. but wouldnt it be just as easy to see " changelog : i tweaked the menu options" and go .." ok i dont care about this update, so im not going to download it" ? rather then just downloading every update? these guys work for pretty much free they can upload it to a dialup site for all i care
yes but i was just saying that to make a point
it would be more relevant for the ~50mb updates or ones with a ton of changes or flashaholics who must stay on the absolute freshest build (like me)
and plus that 1up thing sounds really handy
*wtf magical double post*
i'd jump on board with a standardized process but to support a kernel, rom, and now svn is a pita on a developer....sounds good in theory but in practice i can just see it being a nightmare...if some one were to make some good guides and support those guides then i wouldn't have a problem using it
just remember some ppl that flash roms are not the sharpest spoons in the drawer.
SVN is a pain in the ass, but I suppose I could live with it for someone deployed overseas
Related
All these wonderful ROMs; I am impressed but:
1) I obtained my HTC Touch Pro by trading an unwanted/unneeded old notebook computer for it so kinda sorta in a way I got the phone "for nothing".
Addition: IE: I didn't purposely spent $400 to get this phone. I just got it.
2) I don't really need a pocket PC.
Addition: Not now. Not today. Maybe later.
3) I don't really need a smart phone.
Addition: The key word being "need". All I "need" right now is a phone. I'll trade all the cool fancyness for battery life. My old Straight Talk phone could sit there on standby for a week and not have the battery indicator drop more than a couple notches if even that much. I could use it for all week without charging it. Yes, I know the TP is a Pocket PC and a phone; just making a point.
4) The battery life on this thing is horrible (24 hours on standby costs 20%+ of the battery power) I assume it's because it's doing all those extra Pocket PC/Windows stuff in the background.
Addition: If I charge it before I go out and charge it while I'm out it may last the entire day but likely not.
5) All I really *need* is a camera phone. Phone calls, voicemail, text/media messages, snapshot and video, ...that's about it.
6) The extra unneeded stuff is taking up flash-ram space that could be used for storing pictures and video.
Addition: Strip it all out and I'll have room for lots of pic and videos.
7) Flashing back to the original ROM is easy and takes a few minutes so no harm done by "dumbing-down" the current ROM.
Addition: When I want the smart phone I'll flash on a super-duper all-singing-all-dancing ROM.
8) A Pocket PC is very cool but if I want a portable computer I have a much more powerful very nice netbook that is more or less a part of my body so I don't *need* another computer on my person.
That said, has anybody make a stripped down/basic/bare minumum/no frills/no extras/maximum battery life/minimum flash memory used/no fancy stuff/no wifi/gps/internet connection/nuttin-but-a-camera phone ROM?
Addition: IE: Don't do nothing but make calls and take pictures. Simple. Fast. Maximum battery life. A Dumb Phone (for now anyway).
Thanks.
P.S. No. I don't wish to trade it for a dumb phone. I may some day want a smart phone/Pocket PC but not right now.
Fred Doolie said:
4) The battery life on this thing is horrible (24 hours on standby costs 20%+ of the battery power) I assume it's because it's doing all those extra Pocket PC/Windows stuff in the background.
Click to expand...
Click to collapse
I'm not sure what your expectations are, but only losing 20% in 24 hours is great! I doubt you'll do any better than that. An always active data connection, GPS, and Wi-Fi are the big things that are going to kill battery life, not the OS. I would make sure you have the matching rilphone.dll for the version of radio you are using, however.
Fred Doolie said:
That said, has anybody make a stripped down/basic/bare minumum/no frills/no extras/maximum battery life/minimum flash memory used/no fancy stuff/no wifi/gps/internet connection/nuttin-but-a-camera phone ROM?
Click to expand...
Click to collapse
What you've basically described is a Stock ROM. These are basically just ROMs with the newest build of Windows Mobile and some essential apps, meaning that memory and CPU usage is low. But most of the things that consume battery are switch-off-able, such as the backlight, WiFi, 3G connection, GPS, Bluetooth etc. through the Settings menu or the Comm Manager. If you haven't flashed your phone to a custom ROM yet, you won't get much more basic than the standard 6.1 ROM that your carrier put on the phone to start with.
If you do want Windows Mobile 6.5 but don't want all the frills, you can either be brave and cook a stock-like ROM yourself, or try one from the forums:
[KITCHEN][ROM][WWE][MAR-13-2010] RomRom WM6.5 23547 stock-like Kitchen & ROM is the most updated stock-like kitchen/ROM.
rmcknight:
>I'm not sure what your expectations are, but only losing 20% in
> 24 hours is great!
But that's in Airplane mode (all radios off)! With the radios on it will stand by for about a day before the battery is dead.
Expectations:
"Standby time: Up to 462 hours for WCDMA"
"Talk time: Up to 378 minutes for WCDMA"
http://www.htc.com/www/product/touchpro/specification.html
Reality:
More like up to 120 hours and up to 90 minutes.
---------------------------------------------------------------------
Ben Dude,
>What you've basically described is a Stock ROM.
>meaning that memory and CPU usage is low.
>much more basic than the standard 6.1 ROM that your carrier
>put on the phone to start with.
Sad to hear. The ROM that came with the phone is full of extra stuff and sucks the battery like crazy. The Energy ROM I flashed has even more stuff seems to be easier on battery life. We'll see. This Energy ROM is very cool and maybe I DO want a smart phone right now. The main thing was the battery life. I thought stripping down a ROM would increase battery life due to less stuff running and taking up precious flashram space. Well, SD cards are cheap I guess. I can move as much as possible to external storage.
Maybe I'll have to learn to cook. A stripped-down stock ROM with *everything* removed except phone and camera software. It boots up to a nice wallpaper with two buttons that say "Phone" and "Camera". All radios except phone deactivated. It might be fun to learn how to do that.
Thanks, Guys.
I would happily trade you an LG Xenon for your Fuze.
Fred Doolie said:
rmcknight:
Maybe I'll have to learn to cook. A stripped-down stock ROM with *everything* removed except phone and camera software. It boots up to a nice wallpaper with two buttons that say "Phone" and "Camera". All radios except phone deactivated. It might be fun to learn how to do that.
Thanks, Guys.
Click to expand...
Click to collapse
You can try, but you'll still have to flash the entire operating system; as far as I know it's not as easy as what you've said. I suppose the closest would be a 6.1 ROM without Manila (HTC Sense), no bloatware installed and the hotkeys set as 'phone' and 'camera'. But I doubt that it would be worth trying to truly 'cook out' things like GPS, as they really can be switched off with one button press, and that's probably why nobody does (hence your search for a ROM ).
I've had amazing battery life using the ROM in my sig (dont even think about using android though-- it's fun but not ready for daily use).
install S2U2 -- it makes locking easier but also reduces how often the screen turns on in your pocket. You can set up the screen off delays and such and it saves you a ton of battery life.
Disable the touchflo home screen-- it's pretty superfluous and probably drains battery faster.
If battery life is really bad, consider buying a new one. Check the total talk time (start -> settings -> device information -> call duration) to get an idea of how used the phone is. Those counters don't reset when you flash a new ROM.
try timolols and turn off data.
@ Myrddin
I'll bet you would! Thanks but I want this phone; just trying to make it "My Phone" rather than "Sprint's Phone".
@Storm 717
>I've had amazing battery life using the
> ROM in my sig
I'll try it. As long as I still have my Sprint Picture Mail. It's the only app I really use and need.
>install S2U2 -- it makes locking easier
Been there done that. LOVE it!
>Disable the touchflo home screen
BTDT
>Check the total talk time (start ->
>settings -> device information ->
>call duration) to get an idea of how
>used the phone is.
What you talkin' 'bout, Willis?
See the screenshots.
As long as I have posted them, anybody see a problem with the versions and numbers?
just make sure if you flash to flash a CMDA one and not a GSM rom or you will likely brick your phone
jul644 said:
just make sure if you flash to flash a CMDA one and not a GSM rom or you will likely brick your phone
Click to expand...
Click to collapse
Yes, I've read that and believe it but why? Wouldn't it just not work and then you flash a proper ROM over it?
I know that if you give a little donation to NRGZ or the Capn they can do a perfect ROM for your "need"
Talk to them!
I hate to promote my own ROM, but give my stock-like ROM a try. It's almost exactly what you describe.
Alternatively, I can whip up an even more stripped-down version if you like. Let me know.
.
Fred Doolie said:
Yes, I've read that and believe it but why? Wouldn't it just not work and then you flash a proper ROM over it?
Click to expand...
Click to collapse
its because the amount of voltage/wattage to the radio (the part that connects to the network) is different between gsm and cmda so when you flash a cmda rom on a gsm(sim card)phone then it literally breaks it and also happens vis-versa
response and modification request
jul644 said:
its because the amount of voltage/wattage to the radio (the part that connects to the network) is different between gsm and cmda so when you flash a cmda rom on a gsm(sim card)phone then it literally breaks it and also happens vis-versa
Click to expand...
Click to collapse
Well, that's bad designing. You'd think there would be a check for that in the hardware in case some noobie tech at Sprint/Verizon/AT&T was really tired and tried to update your phone with the wrong ROM. Like a splashscreen saying "GSM Verizon Diamond ROM detected - This is a Touch Pro 1 CDMA Phone" and then it just stops dead on that screen with an endless do-nothing loop.
************
MODIFICATION REQUEST, YOU BRAINS OUT THERE! CAN IT BE DONE?
SAVE US FROM OURSELVES! Can the phones be modified to detect improper ROMs so it doesn't even try to fully boot up/blow up? Some of us are really stu.. frightened noobies.
************
Or a modification in the [one of those files in the RUU folder] that examines the phone and refuses to proceed if the .nbh filoes doesn't match the phone it sees".
Is there any other way to brick a phone. The child in me wants to play with cool stuff but the adult in me says if "it aint broke don't fix it! You don't need a $400 brick"!
* Yes, I know about Hackentosh but don't understand how it works.
On the official HTC site, you can only download a ROM after you type in your phone's serial number, which checks that you have the right hardware for the upgrade. As far as HTC care, this matter has been dealt with. I would guess that techs working for carriers probably have to input your SN too.
There are so many tutorials and guides on this site for first time flashers that if they don't read them first, it's their own fault for being ignorant. Most chefs will warn about it too.
ben_duder said:
Most chefs will warn about it too.
Click to expand...
Click to collapse
Yes but sadly a few don't. I have seen at least one post in the CDMA section that mentions way down "Remove the sim card while flashing the ROM". Oop, that's a GSM phone, no? If I would missed that one line I may have flashed that ROM by accident. Also, a few say something like "For the TP" but don't mention CDMA or GSM anywhere. You have to HOPE it's in the correct section. I just wanted to be 100% safe from accidents.
---
Moot point though; I'm through with flashing. None of the ROMs I found were as smooth and fast as the stock ROM. Beautiful, oh yes, but slow and locking up the phone every little while. It stinks but it runs fine.
I think it's just probably because this site is dedicated to getting the most out of our devices and what you're looking for just doesn't fit in with that. In my experience, I've never had a slow, unstable or just unusable stock ROM. I think your best bet is just to buy a bigger microSD card if you want more space for media, stick with WM6.1 and switch off everything you don't need (3G connection, Wi-Fi, screen brightness, any bloatware, Bluetooth, you know the rest).
With regards to the CDMA/GSM issue, I've never really considered it because I've never been the first to try out a ROM. If it really was posted in the wrong section (which I think is unlikely) it would only take one person other than yourself to flash it and comment before everyone realised. Just make sure you're not that person
Fred Doolie said:
Well, that's bad designing. You'd think there would be a check for that in the hardware in case some noobie tech at Sprint/Verizon/AT&T was really tired and tried to update your phone with the wrong ROM. Like a splashscreen saying "GSM Verizon Diamond ROM detected - This is a Touch Pro 1 CDMA Phone" and then it just stops dead on that screen with an endless do-nothing loop.
************
MODIFICATION REQUEST, YOU BRAINS OUT THERE! CAN IT BE DONE?
SAVE US FROM OURSELVES! Can the phones be modified to detect improper ROMs so it doesn't even try to fully boot up/blow up? Some of us are really stu.. frightened noobies.
************
Or a modification in the [one of those files in the RUU folder] that examines the phone and refuses to proceed if the .nbh filoes doesn't match the phone it sees".
Is there any other way to brick a phone. The child in me wants to play with cool stuff but the adult in me says if "it aint broke don't fix it! You don't need a $400 brick"!
* Yes, I know about Hackentosh but don't understand how it works.
Click to expand...
Click to collapse
First answer is that yes the manufacturers DO in fact have a way to block improper roms. This is why they initially have a CID lock. CID locks prevent the usage of Non-Carrier roms being installed on the phone. Once its had this lock removed, you are able to install non-factory firmwares ( like the ones these wonderful chefs create for us ). In a sense, you take it in your own hands if you flash the wrong firmware for your device, because you have already removed the protection from the carrier.
Second answer. A Hackintosh is computer not made by apple that is running Apples OSX. There are several ways to achieve this, one of which is using an EFI ( Apples Bios Type ) Emulator such as Chameleon or Boot123 , or by using a chipset capable of running the Vanilla ( OEM ) Kernel as is ( Specific Intel chipsets ). I could help direct you to the proper places to discuss this in a PM if you want further information.
Hope those answers helped some
pyraxiate said:
1) CID locks prevent the usage of Non-Carrier roms being installed on the phone.
2) A Hackintosh is computer not made by apple that is running Apples OSX.
Click to expand...
Click to collapse
1) I see. Thanks.
Thought!
The official Sprint upgrade ROM package works on a locked phone. I've installed it. It flashed and worked.
The official Sprint upgrade ROM's .nph file is a signed ROM, right? A signed ROM will get past the CID lock.
You guys are geniuses. Why not put a "sign" code into a cooked ROM for safety? Leave the CID protection in place and let it block incorrect ROMS. Am I being too simplistic?
2) The hackintosh line was a leftover from when I was composing the post. I should have seen and removed it.
My dad just got my mom this Tablet, I dont want to mess with it to much, so no custom roms. All I want to do is give her access to the android market. I have read tons of posts and they all start with open the market then close the market, but I dont have the market. Is there an APK to download to install the market then do the "clear cache till I get an error" fix. Or is the only way to get the market is to install a custom rom that already has the market. Please any help would be greatly appreciated.
Just flash a custom rom and make it run 10 times faster and more stable. The whole process will take less than 20 minutes if you follow my instructions down to the letter.
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
You're either a code green or yellow. Take your pick.
I'm serious about it. The stock rom is really not that great. If you want to maximize the user experience for your mom, flash her a custom froyo rom. I like the calkulin+clemsyn combo the most. Make sure you pay attention to which branch of development you're on.
Ya, I was afraid that was going to be the response. I actually have been on your site for dummies. I am not new to android as I have a Motorola Atrix and have done my share of modding on it, but am nervous about screwing up my moms new present and never hearing the end of it. Gues I might just have to bite the bullet and get it done.
Go on and do it...
goodintentions said:
Just flash a custom rom and make it run 10 times faster and more stable. The whole process will take less than 20 minutes if you follow my instructions down to the letter.
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
You're either a code green or yellow. Take your pick.
I'm serious about it. The stock rom is really not that great. If you want to maximize the user experience for your mom, flash her a custom froyo rom. I like the calkulin+clemsyn combo the most. Make sure you pay attention to which branch of development you're on.
Click to expand...
Click to collapse
I'm 65+.
That said, I went to goodintentions website, followed the instructions, and wala, I have a custom ROM, running at blazing speed and could not be happier.
Calkulin+Clemsyn 1.5ghz Froyo Combo V6 BL1.2
I'd give it a shot.
And don't forget to make a donation to goodintentions...
Moms about to drop the tablet off. Once I find out which branch it is on, I am going to start the process goodintentions has on his "Start Here" page. thanks all for the input.
Goodluck modding the tablet. I put a custom rom on my fathers tablet. Boy did he yell at me as i was halfway through but then he used it that night, called me up and said "holy **** what did you do?" Quite funny in the moment.
Sent from my Galaxy S running Galnet's MIUI v2.2 @ 1.3ghz!
Another vote for Calkulin+Clemsyn 1.5ghz Froyo Combo V6 BL1.2
It's been perfectly solid and stable for me. Your mom shouldn't have any troubles for the foreseeable future.
The good thing is, it's essentially unbrickable, so there's always a way to back out. I assume that she's been using her Tablet since getting it, so she may be used to the UI of stock Tapntap...
That being said, if you flash a rom (another +1 here for Calk+Clem combo 1.6 for bootloader 1.2) and she doesn't like it, you can always take it right back to stock for her. I highly doubt that she'll hate the custom rom, though. She'll have full market access, speed WITH battery management, stockish settings menus, A way to backup the system OS (through CWM) , and basically just a whole new experience that is far superior to stock...
NOW, I'm sure you know, but make sure to backup whatever apps she's already got prior to flashing the new rom...
but, yeah...flash a new rom, let her use it for a few days, THEN ask her which she liked better...
All right, got the new rom and have been playing with and I am quite happy. She only had it for a day or two so I she still was getting use to it. That is why I did it right now before she got to attached to the stock rom. Not seeing the full market but need to do the clear cache and force close thing and see if it will work. I noticed several apps that I wanted to install were not showing up.
smcastillo said:
All right, got the new rom and have been playing with and I am quite happy. She only had it for a day or two so I she still was getting use to it. That is why I did it right now before she got to attached to the stock rom. Not seeing the full market but need to do the clear cache and force close thing and see if it will work. I noticed several apps that I wanted to install were not showing up.
Click to expand...
Click to collapse
In theory, you will never ever have "full" market. Google market is set up so that certain device only gets certain apps. It is impossible for any one device to have access to all apps. Don't ask me why google does this.
My "girlfriend" just bought the transformer. I've been playing with it. Right away, I noticed that the market for the transformer is missing a whole bunch of apps.
That said, if you want more market access, go to the following link and read.
http://viewsonic-gtablet-for-dummies.webs.com/apps/blog/categories/show/1101880-02-market-fix-
smcastillo said:
Moms about to drop the tablet off. Once I find out which branch it is on, I am going to start the process goodintentions has on his "Start Here" page. thanks all for the input.
Click to expand...
Click to collapse
Don't forget to repartition and fix permissions first...
Ya, I actually started on goodintentions site "code green" and did each in order so I should have covered everything. I also did the market fix and I am able to find alot more apps now. I know you will never see everything, but there is alot more apps showing after the clear cache, force close fix.
Background:
Yes it's true, Motorola has every OTA, every non-accepted OTA, and every non-release OTA and sbf sitting on a sever. Special Motorola employees get access to these, even on their phones through the access of the blur cloud. There are 19 servers.
The Goal:
Project Cheesecake was a success on finding a few dev builds for the Defy, Atrix, and Photon which lead to an unlocked bootloader on these devices. There is bound to be something on ONE of these servers, and eventually we'll strike gold and find an unlock. Just takes checking everyday.
How you can help:
Check the servers every change you get! Every phone is a little different, plus keep in mind these are ftp servers, so you might get lucky when you do your scan and you might catch something someone else didn't see before; or you might find something that was uploaded, and then later deleted. Wifi is recommended (but not required) when scanning the servers.
Prerequisites:
You need to use Root Explorer or another file manager with root permissions, because when you find an update, it's going to put it in /cache and you need to copy it from there to the sd card.
Please be on stock 2.3.5 (1.3.412) or 2.3.4 OTA. If you have deleted stuff or are running a custom rom or something, you will need to sbf for this to work.
Getting Started:
1)You need to be on stock latest OTA!!
2) WIPE DATA AND CACHE!!!!
phydo said:
Now an app does it all for you. Imagine that.
1. Okay, so, download THIS APP RIGHT HERE. Edit: Updated link ~ 0vermind
2. Install the app on your phone.
3. Open the app. Click the first button.
4. Reboot.
5. Open app, click second button. Select a server. QA And Staging servers seem most common for updates, but we need to check them all. The default is in Production -> master-blur.whatever.com if you need to get back to it.
6. now click third button in app to check for update. click setup (the moto account thing is bs). Now if it gives you a wifi error, that means the server is down that you chose. If the server is up it will check for an update.
7. If that didn't work, select a new server with button 2, and then check again with button 3.
8. Any comments in this post about the ghettoness or difficulty of scrolling in my app will result in replies including but not limited to A) Slander, B) flaming, and C) death. Try to keep the thread pretty on topic to cheesecake method and other info. I know my app can be refined, jcase has been giving me some tips on streamlining my programming and su permission reduction, but it does good stuff, don't worry. It even remounts system as RO when it uses it.
Click to expand...
Click to collapse
The app does Scroll! It's just a bit tricky! -- I have found that if I longpress an item while scrolling up, it works better.
Thanks for participating!
Update Found
Heyo,
I found one update using Froyo in server 'master-qa3.blurdev.com'. The update seems to be weird. The update on the screen was reported to be '1.3.231.en.us' but the update zip was labeled '1.2.148.en.us' which is the same name as the leaked GB OTA update zip. Nonetheless, this is an interesting development.
Please PM me for the file. I don't want people who don't know what they are doing to abuse it.
I'll continue searching through the server list for any others.
- mostKnownUnknown
mostKnownUnknown said:
Heyo,
I found one update using Froyo in server 'master-qa3.blurdev.com'. The update seems to be weird. The update on the screen was reported to be '1.3.231.en.us' but the update zip was labeled '1.2.148.en.us' which is the same name as the leaked GB OTA update zip. Nonetheless, this is an interesting development.
Please PM me for the file. I don't want people who don't know what they are doing to abuse it.
I'll continue searching through the server list for any others.
- mostKnownUnknown
Click to expand...
Click to collapse
You should also send it to The2DCour
Sent from my DROID X2 using XDA Premium App
mostKnownUnknown said:
Heyo,
I found one update using Froyo in server 'master-qa3.blurdev.com'. The update seems to be weird. The update on the screen was reported to be '1.3.231.en.us' but the update zip was labeled '1.2.148.en.us' which is the same name as the leaked GB OTA update zip. Nonetheless, this is an interesting development.
Please PM me for the file. I don't want people who don't know what they are doing to abuse it.
Click to expand...
Click to collapse
Ahhhh quality assurance is always pretty fruitful Sent ya a pm. Thanks!!
0vermind,
You find anything useful? You and The2Dcour should combine forces. Someone found something for him yesterday.
Sent from my DROID X2 using XDA Premium App
Just saw this post and decided to pop in. Great job starting a Cheesecake for your phone =) Hopefully yes, people will be sending me more files to check. I have made a list of files that I've already checked for Bootloader unlock over at the Pudding thread (shameless plug).
Unfortunately, I didn't find anything. =(
The simpons didn't even register.
Maybe next time...
Yeah. I found two and I gave both of those to the2dcour. There doesn't seem to be a bootloader unlock in both files.
The two I found is when you are in Froyo and in these servers:
master-qa3.blurdev.com - 1.3.231.en.us
master-sdc1.svcmot.com - 1.3.232.en.us
master-blur.svcmot.com - 1.3.232.en.us
After taking a nap and returning the my phone back to normal, it seems like 1.3.232.en.us is the same as the last OTA version/the version that P3droid rooted. It doesn't seem to be a special "Dev" version with that special pudding.
Yeah the simpsons servers and both bqa ones didn't allow you to register.
If anyone still wants to take a look, let me know. You can get the mediafire links from me if you PM me.
My thought so far is that when the Atrix leak was found, Moto was at least thinking about unlocking the bootloader for the Atrix and might have been experimenting with the bootloader when the leak was made. I dunno if we are going to catch a bootloader unlock for the DX2 until Moto makes a serious consideration for unlocking the DX2 with their devs.
With that said, I think this was very successful from an execution standpoint and we need to keep up with regularly checking the servers for update files. I say we should pick random times in checking (not just on a Sat. Morning) and vary it up between location (east coast v. west coast) and Froyo/GB base update.
My only thing is that it took me nearly 5 hours to search through all of the servers after all of the wiping cache and going through Froyo's slow factory reset screens so I hope we can really get a few people dedicated for one or two hours and divide it up.
- mostKnownUnknown
mostKnownUnknown said:
Yeah. I found two and I gave both of those to the2dcour. There doesn't seem to be a bootloader unlock in both files.
The two I found is when you are in Froyo and in these servers:
master-qa3.blurdev.com - 1.3.231.en.us
master-sdc1.svcmot.com - 1.3.232.en.us
master-blur.svcmot.com - 1.3.232.en.us
After taking a nap and returning the my phone back to normal, it seems like 1.3.232.en.us is the same as the last OTA version/the version that P3droid rooted. It doesn't seem to be a special "Dev" version with that special pudding.
Yeah the simpsons servers and both bqa ones didn't allow you to register.
If anyone still wants to take a look, let me know. You can get the mediafire links from me if you PM me.
My thought so far is that when the Atrix leak was found, Moto was at least thinking about unlocking the bootloader for the Atrix and might have been experimenting with the bootloader when the leak was made. I dunno if we are going to catch a bootloader unlock for the DX2 until Moto makes a serious consideration for unlocking the DX2 with their devs.
With that said, I think this was very successful from an execution standpoint and we need to keep up with regularly checking the servers for update files. I say we should pick random times in checking (not just on a Sat. Morning) and vary it up between location (east coast v. west coast) and Froyo/GB base update.
My only thing is that it took me nearly 5 hours to search through all of the servers after all of the wiping cache and going through Froyo's slow factory reset screens so I hope we can really get a few people dedicated for one or two hours and divide it up.
- mostKnownUnknown
Click to expand...
Click to collapse
I wonder what the difference is between 231 and 232. And yeah definitely, as far as I know Moto did promise they would be unlocking all their phones, or at least the ones that came out this year..
mostKnownUnknown said:
Yeah. I found two and I gave both of those to the2dcour. There doesn't seem to be a bootloader unlock in both files.
The two I found is when you are in Froyo and in these servers:
master-qa3.blurdev.com - 1.3.231.en.us
master-sdc1.svcmot.com - 1.3.232.en.us
master-blur.svcmot.com - 1.3.232.en.us
After taking a nap and returning the my phone back to normal, it seems like 1.3.232.en.us is the same as the last OTA version/the version that P3droid rooted. It doesn't seem to be a special "Dev" version with that special pudding.
Yeah the simpsons servers and both bqa ones didn't allow you to register.
If anyone still wants to take a look, let me know. You can get the mediafire links from me if you PM me.
My thought so far is that when the Atrix leak was found, Moto was at least thinking about unlocking the bootloader for the Atrix and might have been experimenting with the bootloader when the leak was made. I dunno if we are going to catch a bootloader unlock for the DX2 until Moto makes a serious consideration for unlocking the DX2 with their devs.
With that said, I think this was very successful from an execution standpoint and we need to keep up with regularly checking the servers for update files. I say we should pick random times in checking (not just on a Sat. Morning) and vary it up between location (east coast v. west coast) and Froyo/GB base update.
My only thing is that it took me nearly 5 hours to search through all of the servers after all of the wiping cache and going through Froyo's slow factory reset screens so I hope we can really get a few people dedicated for one or two hours and divide it up.
- mostKnownUnknown
Click to expand...
Click to collapse
Mannnn... I wish I knew how to do this or what to look for cuz I would be one of the helpers here. I have so much time to sit around and most of it is spent on here ir droidforums.net soooo.... ;(
ashclepdia said:
Mannnn... I wish I knew how to do this or what to look for cuz I would be one of the helpers here. I have so much time to sit around and most of it is spent on here ir droidforums.net soooo.... ;(
Click to expand...
Click to collapse
It's really not that hard. Just follow the instructions in the OP. We would love your help! This project isn't just a one time thing, it's a thing that requires multiple scans every no or then.
The servers that will provide the most luck are the QAs, master-blur, the test server, and the first one.
So I would be doing all this from my phone correct? Don't need a computer just a wifi connect. I want to help but I am on eclipse Rom. It says I need to be stock? Would it work if I was prerooted gb?
Thinkin of making a nandroid of where in at now and when my computer gets going again soon I will be able to sbf back and try some of this.
You have to be on pre rooted gb. When I get home I will package a test build to flash from anything to the required build will everything included. For the sake of progress!
Sent from my DROID X2 using XDA Premium App
Nice work getting stuff like this organized guys. Im hoping it will be only a matter of time now that google has taken over Motorola. I would think they would want to unleash the moto hardware but the agreements with vzw might be in the way. Hopefully they will "allow" the unlock to slip through the cracks if that's the case.
Sent from my DROID X2 using XDA App
Here is some cool info I found. When you are connected to one of the dev clouds:
Dial *#*#4636#*#*
Go To Motorola Services
It will list out a bunch of info regarding the server. Like build date, Blur Version, Server Version, Master Cloud. ect...
hapyman said:
Nice work getting stuff like this organized guys. Im hoping it will be only a matter of time now that google has taken over Motorola. I would think they would want to unleash the moto hardware but the agreements with vzw might be in the way. Hopefully they will "allow" the unlock to slip through the cracks if that's the case.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Company takeovers aren't an instant thing. Even if Google buying up motorola gets bloaders unlocked, we will most likely be too late to the party because once this all goes down, we will be old news.
Sent from my DROID X2 using Tapatalk
Thinking of trying this out between iterations of Eclipse. Gotta get back to stock GB
Here is another build for the X2. http://www.multiupload.com/G5IQI9PL8D. I was thinking of going on this build to search for other builds.
balltongue said:
Here is another build for the X2. http://www.multiupload.com/G5IQI9PL8D. I was thinking of going on this build to search for other builds.
Click to expand...
Click to collapse
What's that? The same sbf as 2.3.3 or is this download link something different that you found?
The sbf is older than the stock froyo build. I thought i was able to unlock the bootloader with this build but its not even in the sbf file.
Anyway its another way for us to get more test builds now that we have 3 sbf's to choose from.
Hi all,
So, I took the leap of rooting my HOX+ (international) about 2 months ago, and the ROM of choice was CM.
I loved it! Love everything about it. At the time, the "stable" channel hadn't been opened, so I was using the version in nightly - it's been moved to stable now - 10.1.
Since I was attached to the stable repo, Goo Manager notified me when 10.2 moved into nightly. After a couple of days of having it stick in my status bar, nagging for an update, I just clicked and let it do its thing.
Unfortunately, this broke my phone . I got an error something along the lines of "the process com.android.phone has stopped". When I tapped "okay" the notification would re-appear after <1 second. I've since found out via Google this is something to do with my kernel (why the auto-update didn't update the kernel too is beyond me =s ) - but at the time, I just wanted a functioning phone with minimal fuss, and thought it'd be best moving myself to stable anyway. This is what I did.
That was Tuesday of this week. Between then and now, the "signal"/reception on the phone (I use Vodafone, so coverage isn't spectacular anyway) has been awful - calls randomly dropping, and it just being unreliable and generally a pain. This is despite it being the supposedly "stable" channel, and the version being the same as the one I installed from nightly (previously). Maturing seemed to make the ROM more buggy, not less!
In the interests of having a working phone, I decided to leave CM. Atm, I'm going to try out an AOKP build - though officially unofficial, I'm hoping that minimalistic => less things to break. We'll see how it goes.
I've run various Google searches and the HOX+ finally seems to be getting (after nearly a year) a good developer community - with Lloir at the forefront of it, and Maxwen's blade kernel. Could anyone recommend a flexible, good looking, regularly updated ROM? I'm not a Sense fan (not long before rooting, Sense 5 came out, and it was "the straw that broke the camel's back" so to speak), but otherwise...I'm not really sure what I'm looking for. GPL would be good, and I'm a fan of minimalism (having as little clutter in the way of unused apps as possible). An active and engaged developer/dev community is a must - I don't want to install software that will become obsolete within a week, and have no prospect of a new release. Other than that, I'm more or less happy to try everything/anything!
Cheers,
AA.
PS - I should probably mention, although I'm in no way a dev, I am quite comfortable with tech, and don't mind spending a bit of time researching things to get stuff working. I'm a dedicated GNU/Linux user, and after a fair bit of distro-hopping I've come full circle to landing on Xubuntu. My view of my phone is basically a more awkward, more delicate version of my PC - the concept of "bricking" a computer is a joke, and I think until this possibility is 100% eliminated on phones, the developer community is always going to be slightly held back. I think the models used for developing Linux OSes could/should be applied to the ROM development process, too - as brilliant as the community is atm, it does have the "exclusive hacker culture" feel to it still.
The kernel didn't update because the device is s-on, also the call dropping bug, is you're problem no one else mentioned it. Just do research on the small amount of ROMs we got.
Sent from my Nexus 5 using Tapatalk
Lloir said:
The kernel didn't update because the device is s-on, also the call dropping bug, is you're problem no one else mentioned it. Just do research on the small amount of ROMs we got.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hi,
How come you can be so sure of the cause? The 'symptom' must be relatively common, I suppose a bit like the technological equivalent of a headache and nausea.
The device is S-ON, you're right. I've read a little but I've not found anything specific to the UK about potential risks. You've got the same phone as me, and you're in the UK too, would you recommend going S-OFF? Does it cause problems with your carrier (I read somewhere that the manufacturer wasn't so bothered, but the carrier was - as it allowed the user to change certain things to do with the way the phone received carrier signal)?
Last bit on ROMs - I've read/seen quite a lot, but the information just isn't out there (unless you personally badger the devs, perhaps). The most official most ROMs get is a thread here. Compare that to (for instance) a Linux distro - you can more or less guarantee that if a distro is linked to on Distrowatch, it'll have it's own site, you can read up about source, included packages, what distinguishing features that OS has, what DE/package manager, etc. There's virtually no equivalent for phones - the best I've seen is xda's ROM listings under the device...if you're lucky one or two of the bigger ones (e.g. CM) will have it's own site. So, in lieu of that, I'm wanting to get a feel of what other users are doing, and what they'd recommend
ArminasAnarchy said:
Hi,
How come you can be so sure of the cause? The 'symptom' must be relatively common, I suppose a bit like the technological equivalent of a headache and nausea.
The device is S-ON, you're right. I've read a little but I've not found anything specific to the UK about potential risks. You've got the same phone as me, and you're in the UK too, would you recommend going S-OFF? Does it cause problems with your carrier (I read somewhere that the manufacturer wasn't so bothered, but the carrier was - as it allowed the user to change certain things to do with the way the phone received carrier signal)?
Last bit on ROMs - I've read/seen quite a lot, but the information just isn't out there (unless you personally badger the devs, perhaps). The most official most ROMs get is a thread here. Compare that to (for instance) a Linux distro - you can more or less guarantee that if a distro is linked to on Distrowatch, it'll have it's own site, you can read up about source, included packages, what distinguishing features that OS has, what DE/package manager, etc. There's virtually no equivalent for phones - the best I've seen is xda's ROM listings under the device...if you're lucky one or two of the bigger ones (e.g. CM) will have it's own site. So, in lieu of that, I'm wanting to get a feel of what other users are doing, and what they'd recommend
Click to expand...
Click to collapse
you cannot S-OFF the X+ currently, so i'm not going into that. Also you stated you flashed from CM10.1 > 10.2, which i assume was a dirty flash (no full wipe etc)
it's like installing the Arch + xubuntu on the same hard drive, which is bound to cause issues. So a full wipe was needed, as you should know "nightlies" are well nightlies, UNSTABLE
the closest we have to distrowatch are the rom reviews and so on. there's my PureAosp, AOSP+ both based on 4.3
CM as well you know what that is.
AOKP no longer supported but stable.
as "best rom" and so on are fround upon, due to the flame and chest beating and so on. which mean's you won't get a good answer tbh, and i'am quite impartial when it comes to rom's as i won't recommend anyone's rom's nor my own.
Lloir said:
you cannot S-OFF the X+ currently, so i'm not going into that. Also you stated you flashed from CM10.1 > 10.2, which i assume was a dirty flash (no full wipe etc)
it's like installing the Arch + xubuntu on the same hard drive, which is bound to cause issues. So a full wipe was needed, as you should know "nightlies" are well nightlies, UNSTABLE
the closest we have to distrowatch are the rom reviews and so on. there's my PureAosp, AOSP+ both based on 4.3
CM as well you know what that is.
AOKP no longer supported but stable.
as "best rom" and so on are fround upon, due to the flame and chest beating and so on. which mean's you won't get a good answer tbh, and i'am quite impartial when it comes to rom's as i won't recommend anyone's rom's nor my own.
Click to expand...
Click to collapse
First thing first, cheers for this man! It's good to be able to have a "conversation" with a dev - although Linux distros have got more infrastructure in place, there is a lack of 1:1 as a result (of having so many devs, etc).
It wasn't a dirty flash at all - every time I've written a new ROM I've wiped everything (or at least, ticked all the boxes in TWRP), then after reformatted - you can see the output of the 'make ext4fs' in front of your eyes. So unless it's that there's some partition which is write-protected (I assume the kernel is - since every time I've had to flash a new kernel - regardless of the wiping in TWRP, the phone just boot-loops without the kernel being flashed)...it's been clean.
I flashed 10.1 BEFORE it was in stable - so my phone was still pointing at the nightly repo (I guess?). GooManager pestered me into updating, and when I did, I ran into issues (presumably, the auto-update isn't intelligent enough to write a new kernel, and/or its in this write-protected partition which can't be accessed from the OS?)
It'd been a while since I'd put 10.1 on, and thought it'd be worth checking to see if it was in stable yet (it was). Did full wipe - as above - and then hit that annoying bug with call dropping. So I'd gone from being working on nightly to broken on stable. Time for a new ROM, methinks...looked around, and decide to post here.
As things stand I'm using AOKP (just because it was another popular ROM I knew, not really for any other reason). It's doing my head in though - either I'm being thick, or there's no option to edit settings in ANY app. I'm missing some of the gloss CM has too, things like it coming with a File Manager installed (why the hell would you not have one?!). From what you say, flashing 10.1 might be worth trying again...I'll go through from ground 0 and hopefully it won't break this time.
I get the thing with not wanting to advertise...so instead can I ask what you yourself use on your HOX+? Do you use it as a main phone, or is it just something you use for developing?
ArminasAnarchy said:
(presumably, the auto-update isn't intelligent enough to write a new kernel, and/or its in this write-protected partition which can't be accessed from the OS?)
I get the thing with not wanting to advertise...so instead can I ask what you yourself use on your HOX+? Do you use it as a main phone, or is it just something you use for developing?
Click to expand...
Click to collapse
you are right on point 1, it's in the write protected partition, and 2nd point, i tend to use my own rom's....i'am in the mindset, if i don't use my own rom's why should other people?
Lloir said:
you are right on point 1, it's in the write protected partition, and 2nd point, i tend to use my own rom's....i'am in the mindset, if i don't use my own rom's why should other people?
Click to expand...
Click to collapse
Haha, I see the logic!
Okay: so we've narrowed it down to a kernel issue. With my AOKP flash, what I did (blade wasn't for the right Android version I think) was extracted the .img file from the ROM.zip and flashed that.
With CM 10,1 (i.e. stable channel) - in your opinion would it be better to do the same, or use the blade kernel?
ArminasAnarchy said:
Haha, I see the logic!
Okay: so we've narrowed it down to a kernel issue. With my AOKP flash, what I did (blade wasn't for the right Android version I think) was extracted the .img file from the ROM.zip and flashed that.
With CM 10,1 (i.e. stable channel) - in your opinion would it be better to do the same, or use the blade kernel?
Click to expand...
Click to collapse
ALL my rom's are extract kernel from zip, i'am not sure what max did with his AOKP.....but 100% all mine you pull from zip and flash that
you can try the CM10.2 btw M1 not long ago released....just an idea..
Lloir said:
ALL my rom's are extract kernel from zip, i'am not sure what max did with his AOKP.....but 100% all mine you pull from zip and flash that
you can try the CM10.2 btw M1 not long ago released....just an idea..
Click to expand...
Click to collapse
Re-installed 10.1 (stable) again. Same issue, even though I've only had it running for 24 hours, it's dropped the call and didn't seem able to get 3G data (it was stuck at "E" for some reason, which makes doing anything impossible) despite being in the middle of the city and not near anything obvious that should block it like a huge block of flats etc.
I installed 10.2, we'll see how it goes.
Please bear with me on this - it will end up with me asking which rom to use (so, mods - if you must delete it, I've been honest up front) but I do have a specific need.
I have had my S3 since August 2012. It's been on Android 4.1 until the recent update to 4.3. All that time I have been really unhappy with the performance. I've not rooted it or changed any kernels/roms - I've been a good boy and stuck with Samsungs TouchWiz and their interpretations.
But the performance is diabolical. It can take 7 seconds (I've timed it) from when I touch the phone icon on the main screen to when the number pad appears so I can actually phone someone. Sometimes its quicker - but never less than 2 seconds. Other apps are equally as bad.
I have tried everything I can think of to speed it up. I've got no animation (I've enabled developer mode) and done anything I can see to try and make it work at a reasonable speed. I've even done a complete wipe and reset and re-loaded my apps - no difference.
OK, you say - but what are you running? Well, not much. I use my phone as a phone, to check emails (my works email, so I have to have Afaria as a security app) and to read Kindle books. Occasionally I will use it to surf the internet using Dolphin. I have a 16Gb microSD card with my music on it which I listen to when I am in the gym. I've put on MicroCPU Monitor so I can see if the CPU is clogging up (it's not). That's about it. I don't play games.
So, now we come to the question. Is there anything I can do without putting a new ROM on to make it work at what I consider a good speed? If not (and here is where the mods will get me), which ROM will give me speed? I'm not after fancy features, I just want a ROM that makes my phone work like a phone - not a lump of electronics with a mind of its own. [I do know how to root and upgrade as I have a Nexus 10, Nexus 7 and an HP TouchPad]
I would appreciate some answers or at least ask me more questions that I can go and investigate.
Thanks for any advice.
Alan
alan sh said:
Please bear with me on this - it will end up with me asking which rom to use (so, mods - if you must delete it, I've been honest up front) but I do have a specific need.
I have had my S3 since August 2012. It's been on Android 4.1 until the recent update to 4.3. All that time I have been really unhappy with the performance. I've not rooted it or changed any kernels/roms - I've been a good boy and stuck with Samsungs TouchWiz and their interpretations.
But the performance is diabolical. It can take 7 seconds (I've timed it) from when I touch the phone icon on the main screen to when the number pad appears so I can actually phone someone. Sometimes its quicker - but never less than 2 seconds. Other apps are equally as bad.
I have tried everything I can think of to speed it up. I've got no animation (I've enabled developer mode) and done anything I can see to try and make it work at a reasonable speed. I've even done a complete wipe and reset and re-loaded my apps - no difference.
OK, you say - but what are you running? Well, not much. I use my phone as a phone, to check emails (my works email, so I have to have Afaria as a security app) and to read Kindle books. Occasionally I will use it to surf the internet using Dolphin. I have a 16Gb microSD card with my music on it which I listen to when I am in the gym. I've put on MicroCPU Monitor so I can see if the CPU is clogging up (it's not). That's about it. I don't play games.
So, now we come to the question. Is there anything I can do without putting a new ROM on to make it work at what I consider a good speed? If not (and here is where the mods will get me), which ROM will give me speed? I'm not after fancy features, I just want a ROM that makes my phone work like a phone - not a lump of electronics with a mind of its own. [I do know how to root and upgrade as I have a Nexus 10, Nexus 7 and an HP TouchPad]
I would appreciate some answers or at least ask me more questions that I can go and investigate.
Thanks for any advice.
Alan
Click to expand...
Click to collapse
If u rly wan speed over features. Aosp roms. Cyanogenmod is one of them tat has the most similarities to stock android on ur nexus.
Sent from my GT-I9300 using xda app-developers app
alan sh said:
Please bear with me on this - it will end up with me asking which rom to use (so, mods - if you must delete it, I've been honest up front) but I do have a specific need.
I have had my S3 since August 2012. It's been on Android 4.1 until the recent update to 4.3. All that time I have been really unhappy with the performance. I've not rooted it or changed any kernels/roms - I've been a good boy and stuck with Samsungs TouchWiz and their interpretations.
But the performance is diabolical. It can take 7 seconds (I've timed it) from when I touch the phone icon on the main screen to when the number pad appears so I can actually phone someone. Sometimes its quicker - but never less than 2 seconds. Other apps are equally as bad.
I have tried everything I can think of to speed it up. I've got no animation (I've enabled developer mode) and done anything I can see to try and make it work at a reasonable speed. I've even done a complete wipe and reset and re-loaded my apps - no difference.
OK, you say - but what are you running? Well, not much. I use my phone as a phone, to check emails (my works email, so I have to have Afaria as a security app) and to read Kindle books. Occasionally I will use it to surf the internet using Dolphin. I have a 16Gb microSD card with my music on it which I listen to when I am in the gym. I've put on MicroCPU Monitor so I can see if the CPU is clogging up (it's not). That's about it. I don't play games.
So, now we come to the question. Is there anything I can do without putting a new ROM on to make it work at what I consider a good speed? If not (and here is where the mods will get me), which ROM will give me speed? I'm not after fancy features, I just want a ROM that makes my phone work like a phone - not a lump of electronics with a mind of its own. [I do know how to root and upgrade as I have a Nexus 10, Nexus 7 and an HP TouchPad]
I would appreciate some answers or at least ask me more questions that I can go and investigate.
Thanks for any advice.
Alan
Click to expand...
Click to collapse
Maybe this Afaria thing is causing the problem. It is a security app, so maybe it is running scans, checks etc on the background.
Since you are unrooted i dont know how you can check if it is the culprit... maybe checking your battery statistics can give an idea.
Other option would be to start fresh. Root the phone and install whichever ROM you like and check the performance without installing your apps.
Then install the apps one by one and check which one is the culprit.
*** Dont forget to Backup***
alan sh said:
Please bear with me on this - it will end up with me asking which rom to use (so, mods - if you must delete it, I've been honest up front) but I do have a specific need.
I have had my S3 since August 2012. It's been on Android 4.1 until the recent update to 4.3. All that time I have been really unhappy with the performance. I've not rooted it or changed any kernels/roms - I've been a good boy and stuck with Samsungs TouchWiz and their interpretations.
But the performance is diabolical. It can take 7 seconds (I've timed it) from when I touch the phone icon on the main screen to when the number pad appears so I can actually phone someone. Sometimes its quicker - but never less than 2 seconds. Other apps are equally as bad.
I have tried everything I can think of to speed it up. I've got no animation (I've enabled developer mode) and done anything I can see to try and make it work at a reasonable speed. I've even done a complete wipe and reset and re-loaded my apps - no difference.
OK, you say - but what are you running? Well, not much. I use my phone as a phone, to check emails (my works email, so I have to have Afaria as a security app) and to read Kindle books. Occasionally I will use it to surf the internet using Dolphin. I have a 16Gb microSD card with my music on it which I listen to when I am in the gym. I've put on MicroCPU Monitor so I can see if the CPU is clogging up (it's not). That's about it. I don't play games.
So, now we come to the question. Is there anything I can do without putting a new ROM on to make it work at what I consider a good speed? If not (and here is where the mods will get me), which ROM will give me speed? I'm not after fancy features, I just want a ROM that makes my phone work like a phone - not a lump of electronics with a mind of its own. [I do know how to root and upgrade as I have a Nexus 10, Nexus 7 and an HP TouchPad]
I would appreciate some answers or at least ask me more questions that I can go and investigate.
Thanks for any advice.
Alan
Click to expand...
Click to collapse
You could try two things.
First: root your phone.
Second: find and apk called Seeder, this apk increase your phone speed reducing the lag and really works.
Here's the link: http://forum.xda-developers.com/showthread.php?t=1987032
Standard reply first factory reset .
knarfyo said:
You could try two things.
First: root your phone.
Second: find and apk called Seeder, this apk increase your phone speed reducing the lag and really works.
Here's the link: http://forum.xda-developers.com/showthread.php?t=1987032
Click to expand...
Click to collapse
Thanks for all the replies.
So far, I have done a hard reset and loaded only AI keyboard plus (my favourite keyboard). I'll have a look at Seeder as well.
Alan