[TOOL/DEV Q] My username is Cynagen, I'm a flashaholic - LG Thrill 4G
I've recently come to the conclusion that I'm a flash-a-holic, and in order to facilitate my need for speed from my device, extended battery performance, and just the best overall experience from my phone (it's been a LONG time since I've ever been completely happy with one of my phones), I have started drawing up specs for an all-around Thrill tool which will incorporate all the tools into a fully automated process (with prompts for certain things of course asking that you confirm the action has been done if it can't be detected) to help speed up the process and take some of the guess work out of it all.
All-in-all I've reflashed my Thrill about 20+ times in the past 3 months, and while I've 'settled' for now, I see that with the hopefully upcoming ICS release, and the daunting task of flashing that is presented to all users currently, a tool which incorporates all steps of the process and attempts to simplify it to "Select which ROM you wish to flash" "it is recommended that you use X baseband for that ROM, however you can choose another at your own risk", and click Go, the rest of the process is handled by the tool, might be desired.
The aim of this tool would be to make first time flashers a little less intimidated by the plethora of steps required by simplifying them down as much as possible and handling as much as possible in the background. However it would also provide flash-a-holics like myself a quick system by which to refresh the ROM on the phone or switch to another to try it out.
Steps I'd like to see the tool perform for folks:
Flash baseband/stock ROM
Rooting (based on which version you select, it will select either SuperOneClick or Megatron automatically.)
Installing CWM (Touch only for select ROMs (or override with warning), regular otherwise for everyone else)
Copy to phone as update.zip the desired ROM
Optionally, should an overclocked Kernel be selected, afterwards, another update.zip for the Kernel.
I'd like some thoughts on this and some guidance before I start really digging in. Couple of my main questions are as follows:
First, is this even needed anymore with the plethora of information available? Yes, it coalesces most of those steps documented into a simple interface tool, however do people prefer to keep everything broken up, I know I don't, especially when it's all towards one goal.
If there is still a need/desire for a tool like this, how in-depth on options would people like to get?
What would the developers like to see available from a developer's standpoint?
What would the end-users like to see available from the interface?
I would love any feedback on this idea before I move forward so I have a clear picture of what it is that the community would like.
Thank you for your time and feedback folks.
Welllll.
Acidhazard kitchen rom I know you have used. The build interface Is a great format to start with. Has a few automated tools built in. Probably a novice or advanced select. That would appeal to newbie and testers alike . An updatable base and tool would be great. Hunting for base bands is a pain and having it all in one handy tool would be lovely.
This is a good idea. I would make it so it cannot flash a ROM if the correct baseband isn't there to help new people avoid bricks. I think that is the biggest fear for people new to flashing.
Sent from my LG-P925g using xda app-developers app
SithLord2K said:
This is a good idea. I would make it so it cannot flash a ROM if the correct baseband isn't there to help new people avoid bricks. I think that is the biggest fear for people new to flashing.
Sent from my LG-P925g using xda app-developers app
Click to expand...
Click to collapse
The only way you would be allowed to override the baseband is if you were in advanced mode and filled in a checkbox accepting the consequences of your choice. I've had wrong baseband before and had a working phone with no service. It's possible it's not fun but it's possible, and yes, for basic mode it would be forced to only the accepted list of basebands for the ROM you wish to install.
Cab121 said:
Welllll.
Acidhazard kitchen rom I know you have used. The build interface Is a great format to start with. Has a few automated tools built in. Probably a novice or advanced select. That would appeal to newbie and testers alike . An updatable base and tool would be great. Hunting for base bands is a pain and having it all in one handy tool would be lovely.
Click to expand...
Click to collapse
The idea here is not to duplicate somebody else's work, but instead augment it and enhance it further. While his tool is awesome, it's also command line, my tool will end up being a user-friendly GUI. I would love to end up with a multi-ROM kitchen for the O3D and Thrill (P920 & P925 respectively) built into this tool, it's not a priority for the beginning. I will be studying heavily the scripts used by some of these wonderful tools in an effort to duplicate their efforts contained within a GUI. I don't plan on writing something that just runs these tools in the background and makes the selections for you, I'm talking a complete tool from the ground up. I think I may write a helper tool for inclusion to the ROMs it builds which I can use to help facilitate this process in a much more friendly manner. (So you have to touch the phone less.)
Cynagen said:
The only way you would be allowed to override the baseband is if you were in advanced mode and filled in a checkbox accepting the consequences of your choice. I've had wrong baseband before and had a working phone with no service. It's possible it's not fun but it's possible, and yes, for basic mode it would be forced to only the accepted list of basebands for the ROM you wish to install.
The idea here is not to duplicate somebody else's work, but instead augment it and enhance it further. While his tool is awesome, it's also command line, my tool will end up being a user-friendly GUI. I would love to end up with a multi-ROM kitchen for the O3D and Thrill (P920 & P925 respectively) built into this tool, it's not a priority for the beginning. I will be studying heavily the scripts used by some of these wonderful tools in an effort to duplicate their efforts contained within a GUI. I don't plan on writing something that just runs these tools in the background and makes the selections for you, I'm talking a complete tool from the ground up. I think I may write a helper tool for inclusion to the ROMs it builds which I can use to help facilitate this process in a much more friendly manner. (So you have to touch the phone less.)
Click to expand...
Click to collapse
When you ready my scripts, just know, it's in English. Lmao.
Literally, command prompt code.
The Dark Lestat said:
When you ready my scripts, just know, it's in English. Lmao.
Literally, command prompt code.
Click to expand...
Click to collapse
This isn't my first ro-day-oh here guys... I'm the bastard that wrote the PeerGuardian 2 Vista Loader to get PG2 working on Vista when it was still in beta (and buggy as hell).
Cynagen said:
This isn't my first ro-day-oh here guys... I'm the bastard that wrote the PeerGuardian 2 Vista Loader to get PG2 working on Vista when it was still in beta (and buggy as hell).
Click to expand...
Click to collapse
Oh, that's not it. Every time someone opens my script, they ask why they can understand it.
Sent from my Samsung Galaxy S II w/AOKP
The Dark Lestat said:
Oh, that's not it. Every time someone opens my script, they ask why they can understand it.
Sent from my Samsung Galaxy S II w/AOKP
Click to expand...
Click to collapse
LMFAO most languages are surprisingly in english, it's kinda weird, cause I know a couple that were NOT developed here in America or the UK.
Cynagen said:
This isn't my first ro-day-oh here guys... I'm the bastard that wrote the PeerGuardian 2 Vista Loader to get PG2 working on Vista when it was still in beta (and buggy as hell).
Click to expand...
Click to collapse
Then you are also my hero. That came in handy when the rest of us where screaming at our machines having dealt with Vista and any torrent work.
I was under the impression your original plan here was to utilize the tools and data available from various sources "AcidHazard, Megatron and so on" to achieve the wonderful multipurpose and expandable tool you have decided to develop. We are here to help. More especially since your calling upon it. Plenty of communication , feedback, and patience is what I prescribe here. That being laid out :fingers-crossed: we can continue.
Ok so with all respect, credentials, history, contribution, and hero work established and being taken in to consideration as I type lets define a few of your plans further and designs ideas further so we might better contribute to your efforts. This is an awesome idea and I think its something we all need desperately. I realise the following will seem very redundant and you may feel its unnecessary but trust me it will help everyone from this point on.
Question 1
The principal function of this tool is to perform the primary tasks associated with rooting, flashing, and customizing? This would initially entail the following core tasks?
Flash baseband/stock ROM
Rooting (based on which version you select, it will select either SuperOneClick or Megatron automatically.)
Installing CWM (Touch only for select ROMs (or override with warning), regular otherwise for everyone else)
Copy to phone as update.zip the desired ROM
Optionally, should an overclocked Kernel be selected, afterwards, another update.zip for the Kernel.
Question 2
Your plan is to use and or augment current work and material already available to achieve the majority of the above tasks essentially wrapping it all up in a very nice and tidy singe tool?
Question 3
Your goal in the front or interface is to have a GUI and stay away from automated command line ?
Question 4
How in depth and to what degree did you want to deal with any updates. Baseband and so on? Will files pull from a server, file host or other source? Or shall it be with the interface itself and the user hunts for the files then points to where they are located?
Question 5
How will devs offer there roms to your tool? Probably directly related to Q4.
Question 6
Where the heck is Waldo?
Question 7
Can you provide us with a little copy paste form for us to add feature requests? Should make things much simpler when your sifting threw the thousand posts your gonna get when this thing is live.
(continued)
Question 8: Why is this not in General?
Anyway, I think that some bits are pretty much impossible, for example flashing the baseband since you need the LGMobileTool for that or SmartFlash, command prompt or adb or fastboot won't work for this at all. Otherwise I would say it's doable, but it probably won't be from me unless I remember to do it in December and no one else has done it yet :/
Cab121 said:
Then you are also my hero. That came in handy when the rest of us where screaming at our machines having dealt with Vista and any torrent work.
I was under the impression your original plan here was to utilize the tools and data available from various sources "AcidHazard, Megatron and so on" to achieve the wonderful multipurpose and expandable tool you have decided to develop. We are here to help. More especially since your calling upon it. Plenty of communication , feedback, and patience is what I prescribe here. That being laid out :fingers-crossed: we can continue.
Ok so with all respect, credentials, history, contribution, and hero work established and being taken in to consideration as I type lets define a few of your plans further and designs ideas further so we might better contribute to your efforts. This is an awesome idea and I think its something we all need desperately. I realise the following will seem very redundant and you may feel its unnecessary but trust me it will help everyone from this point on.
Question 1
The principal function of this tool is to perform the primary tasks associated with rooting, flashing, and customizing? This would initially entail the following core tasks?
Flash baseband/stock ROM
Rooting (based on which version you select, it will select either SuperOneClick or Megatron automatically.)
Installing CWM (Touch only for select ROMs (or override with warning), regular otherwise for everyone else)
Copy to phone as update.zip the desired ROM
Optionally, should an overclocked Kernel be selected, afterwards, another update.zip for the Kernel.
Question 2
Your plan is to use and or augment current work and material already available to achieve the majority of the above tasks essentially wrapping it all up in a very nice and tidy singe tool?
Question 3
Your goal in the front or interface is to have a GUI and stay away from automated command line ?
Question 4
How in depth and to what degree did you want to deal with any updates. Baseband and so on? Will files pull from a server, file host or other source? Or shall it be with the interface itself and the user hunts for the files then points to where they are located?
Question 5
How will devs offer there roms to your tool? Probably directly related to Q4.
Question 6
Where the heck is Waldo?
Question 7
Can you provide us with a little copy paste form for us to add feature requests? Should make things much simpler when your sifting threw the thousand posts your gonna get when this thing is live.
Click to expand...
Click to collapse
Question 1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The principal function of this tool is to perform the primary tasks associated with rooting, flashing, and customizing?
Yes, with the goal of expanding over time to include such things as a kitchen for all thrill ROMs like the acidhazard kitchen. Possibly even the UOT.
Question 2
Your plan is to use and or augment current work and material already available to achieve the majority of the above tasks essentially wrapping it all up in a very nice and tidy singe tool?
That's a possibility however it makes more sense to convert most of these tools into the native language of the new tool. For initial purposes this will be AutoIt. Should enough Linux and Mac interest be generated a PHP using GTK front-end with the autoit version becoming depreciated.
Question 3
Your goal in the front or interface is to have a GUI and stay away from automated command line ?
The goal is to write one EXE to incorporate all tools needed for the basic flashing functionality needed to go from anything to stock and follow the process up to custom ROM and kernel. From there, again with sufficient feedback, development would continue and new features incorporated. Backend tools can change how they operate thus requiring a new patch every version, processes don't change too much and keeping up with developments won't be as hard. This in turn frees up time to design an actual gui over using automated command-line.
Question 4
How in depth and to what degree did you want to deal with any updates. Baseband and so on? Will files pull from a server, file host or other source? Or shall it be with the interface itself and the user hunts for the files then points to where they are located?
Updates for things such as what you listed? Basebands, ROMs, necessary tools like adb, and the like? Why not all of those wonderful ideas? This will give ease of access during operation and once depreciated for years the option to pack the tool in a zip file with their favorite ROMs and modifications ready to be used once unpacked.
Question 5
How will devs offer there roms to your tool? Probably directly related to Q4.
Many options are available, private hosting, directly submitting to the project website (which will keep the tools files up to date automatically), allowing users to download and select locally.
Question 6
Where the heck is Waldo?
I haven't the foggiest.
Question 7
Can you provide us with a little copy paste form for us to add feature requests? Should make things much simpler when your sifting threw the thousand posts your gonna get when this thing is live.
Do you one better, an email address. I use my forum posts as tech support for the application, so things don't end up cluttered. Yes it means I'm bound to get two or more emails regarding the same suggestion but that's fine by me if it means that the public information is directly useful.
Sent from my LG-P920 using xda app-developers app
moved to general.
Only thing else I can think of that would be a huge advantage would be a theme compiling tool and a debug log that could be used as a resource for you and the Devs who work on the roms. Can't wait to see what you create because even 1/2 of this would be awesome.
Cab121 said:
Only thing else I can think of that would be a huge advantage would be a theme compiling tool and a debug log that could be used as a resource for you and the Devs who work on the roms. Can't wait to see what you create because even 1/2 of this would be awesome.
Click to expand...
Click to collapse
A theme compiling tool is harder to make than you think. Even compiling a theme is hard to do if you don't know what you're doing.
Heck. I had a hard time compiling a theme, but then again, LG borked everything so I had to do the run around.
The Dark Lestat said:
A theme compiling tool is harder to make than you think. Even compiling a theme is hard to do if you don't know what you're doing.
Heck. I had a hard time compiling a theme, but then again, LG borked everything so I had to do the run around.
Click to expand...
Click to collapse
Very true. I have not done it so I can't really offer a valid opinion. Would be awesome though albeit a pipe dream lol.
Cab121 said:
Very true. I have not done it so I can't really offer a valid opinion. Would be awesome though albeit a pipe dream lol.
Click to expand...
Click to collapse
If somebody else has the process mapped out already, I'm looking at you Lestat, I can clone it and present it in an easy to manage fashion that can be adopted by many users. This is only if steps are documented, I don't exactly have time to do any research into hacking an Android.
Cynagen said:
If somebody else has the process mapped out already, I'm looking at you Lestat, I can clone it and present it in an easy to manage fashion that can be adopted by many users. This is only if steps are documented, I don't exactly have time to do any research into hacking an Android.
Click to expand...
Click to collapse
I don't have it mapped out, but I can map it out pretty quickly.
Here's a ROUGH draft.
First, there can be two types of "theme kitchens".
Automatic
Non-Automatic
An automatic theme kitchen is usually going to be for one device.
A non-automatic theme kitchen can be used for a broad range of devices.
Automatic - Not familiar with code
Non-Automatic - Familiar with code.
Here's the draft for the automatic, and yes, I'm typing this as I go. Lol
Automatic
Extract theme files from phone. (usually framework-res.apk & SystemUI.apk for Gingerbread)
Decompile theme files
Choose what theme element you want
Automatically overwrite UI element (.pngs, .xmls, and other files) - Go back to number 3 UNTIL the loop is closed. (Finished with theme)
Compile theme files
Push files to phone
Set permissions
Wipe dalvik-cache and cache
Reboot phone
/End
Here's the draft for the Non-automatic.
Non-Automatic
Extract theme files from phone. (usually framework-res.apk & SystemUI.apk for Gingerbread)
Decompile theme files
USER APPLIES THERE OWN THEME ELEMENTS
Compile theme files
If error occurs while compiling, go back to number 3.
Push files to phone
Set permissions
Wipe dalvik-cache and cache
Reboot phone
/End
Just a simple map of what to do. Of course, putting it into code is a lot easier when you have the correct files.
They need flashaholics anonymous. Then maybe I wouldn't flash people on the streets. >_>
Oops, wait. Wrong subject matter.
P.S. This was just a joke, something to get a laugh out of people.
cmarriner82 said:
They need flashaholics anonymous. Then maybe I wouldn't flash people on the streets. >_>
Oops, wait. Wrong subject matter.
P.S. This was just a joke, something to get a laugh out of people.
Click to expand...
Click to collapse
Dood, back when I had my netbook I used to flash people on the street all the time, the ones with some time and a couple bucks.
P.S. I totally loved your joke and well, had to answer honestly, as a joking response, even though I used to do this exact thing.
Anywhos... I expect to have a test-tool released next week which when you run it, it will allow me to collect some data on the environments (submitted anonymously back to my dev box), ask you a few questions, and collect some data from the phones themselves if they are connected and in debug mode at that time (which I hope everyone does as this is HUGELY important). With the test tool, I'll have it report whether or not your phone will be supported as it stands right now (plug and play), or at least recommend changes (drivers, software, phone version, etc) to make it compatible.
I'm also thinking of the name "Thrilling Toolkit" for the end product, what do you all think?
Sounds good. Can't wait to try it.
Sent from my LG-P925 using xda app-developers app
Related
Linux Question
This might sound really odd... but I'm looking to -NOT- use my g1 as a phone... I want to uh... (shoot me if you must) want to remove Android, and install a very light ubuntu install or other gnu/linux derivative like DSL (which cannot be ported to armel probably) to my phone and use it as a mini mini computer... my question to the DREAM community on XDA here is... can it be done... and for any reason I ever want to go back... do you think it'd be reversible? My main reasoning is this... I have a nokia 5310, and I work a crappy produce job at a supermarket... I fear my G1 getting broken, and have not used it in the last 2 months. also, I'd be interested in learning how to work stuff out and try to get androided ported over to the new 3g Dash if that was possible, cause that phone looks very nice... IMHO though so... please criticism and responses of all kinds welcome to this question.
The closest I've seen is installing Debian with only terminal =/ sorry. You can look under development for more info.
well actually... with vncviewer you can uh... vnc to it and have x11 running with icewm or lxde vnc viewer local host
I'm not pro at this. Sorry if my advice was bad. lol
No not bad... but good... thank you. I am looking for "ANY" information... and you fit the requisites. Thanks friend
The reason for running x11 and debian on top of android through vnc is that drivers for the g1 hardware aren't available. Unless you want to write these drivers yourself, I'd forget this one. By the time you get it working, your g1 will be fossilised.
I'd be willing to go and try to learn how to do it. it'd be a fun project... i mean the thing is just sitting here... I mean... I could always perhaps make a completely stripped down version of android. I only want it to use Wi-Fi... and that's pretty much it... I just want it to be an MID
I want to make sure I understand the situation: 1) You have a cheaper phone so do not use the G1 for fear of damaging it. 2) Since you do not use the G1 you want to: - tinker with it, most likely destroying it in the process if you succeed at anything. - install a more conventional Linux distro on the phone, which will require at least some programming knowledge as well as intimate knowledge of Linux. If you want X then it as gone from challenge to an impressive feat. and finally 3) You want to port android to the Dash 3G. Your decision making process is a little questionable, but hopefully there is some reasoning I missed or you did not mention. My advise to you would be: Please learn to walk before you attempt to fly. A stripped down android would be more feasible. You would not have X, but you should be able to port quite a bit of commandline tools over, to include a more user friendly shell. Then you could try and cross compile X, which will take a lot of patience. If you manage to succeed though. from that point you could do a headless X session and attach to it vian VNC in much the same way as is currently done with debian. Alternatively you could try and port the G1 drivers over to the freerunner project and work from that direction, but this would be much more difficult. It seems a terrible waste of time in my opinion but if you want to try, go for it. Personally I say sell the G1 and buy a nokia n810. It is a little larger but still small and is a mid. If however you are set on this course I would suggest hanging out on the IRC channels and getting advice from the ROM cookers, Cyanogen in particular since he rebuilds the linux kernel for the G1, something you will be doing a lot of.
Well most birds learn to fly before they walk. And I think I will go down the trail of a custom Android build. I just wanted to know of it being possible to make it work. I mainly refer to the fact I didn't want it to break ie the screen or the digitized I assume you mean the xda channel... ... so yes I will choose to jump into the pool before the water is full in it thank you for the advice and knowledge
Individual Phone power.
I honestly couldn't think of a good title, and I was half and half about posting this in the themes/wallpaper section or developement. But ever since we started partitioning our sd cards I always felt like that was something we should be able to do through our phones, mainly because I lacked resources to download and run everything. And now I'm thinking it would be very nice if we had a feature to customize our phones without using our PC's or MAC's! I could go into detail about what to include but I'm sure we all know what we want to see done. And besides, the HTC Sapphire has that FreshFace app that looks ok, but lets out due that app already and build something along these lines of deeper, better, more personal customization. No offense to any theme makers I appreciate all your work.
This should be in the apps section, definitely not development. How about Open Home or aHome? Or better yet, you can create your own theme and it would be completely customized
Diceman4 said: This should be in the apps section, definitely not development. How about Open Home or aHome? Or better yet, you can create your own theme and it would be completely customized Click to expand... Click to collapse Lol I would if I was educated enough in the manner, I'd pretty much make whatever anyone wanted because I think its pretty interesting. Just given my enviorment of a family p.c. and a small notebook, I doubt I'll have the right time to learn and all that buddy.
android being open source "is" what you speak of in terms of customization already.. problem is that it "is" customization only by the ones who speak the language of Java. Themes or whatnot can be done with resigning new images into a update.zip without too much learning curve if you know how to do graphics. The ones without the talent.. like hyenas.. just take what they can get and get by on xda lurking. I started closest to the last statement and am now currently at the second where I can comfortably change graphics and use adb and signing apk as I please. This lets me pretty much change anything minus the rom and os itself that requires coding. I just got my second bill from t-mo. Just do it.
Android Devs: What are the biggest challenges in porting Android to Xperia X1?
The intent of this thread was to provide a consolidated answer to all of those waiting patiently (some, not so patient) for a complete Android ROM for the SE Xperia X1. Many perceive Android as "a hacker's OS" because it is both open source, and supported on so many other HTC devices. Because of this, I suspect many of the "spectators" here (like me) incorrectly assumed that Android on Kovsky (or, any HTC smartphone) would be a straight forward affair, considering some of the amazing work done here with the Windows Mobile ROMs. It seems, however, that creating a usable Android ROM for Xperia is far more difficult than creating WM6 ROMs? Android has been out for quite some time and there's still no widely available Android ROM for Xperia X1. It is for this reason that I've started this thread. I'd like to hear from those that have/are working on Android about the challenges in putting together an Android ROM for Xperia X1. What has contributed to this being a difficult OS to port to Kovsky? Is it driver support? Perhaps Kovsky has a unique selection of hardware that complicates the process? Or, has much of the effort been directed towards Haret vs. a native ROM? If so, why? Can the Haret work be merged into an effort to create an Android ROM or are these different approaches completely exclusive to one another? Perhaps there are IP/DRM/license issues that are complicating the effort? I'd very much like to hear from ROM chef and devs working on this port. While it may seem like a idealist perspective, I wonder if some dialog on the issues surrounding an Android port/ROM might result in greater community involvement, and ultimately a stellar Android ROM for one of HTC's most beautiful smartphones. I'm certain that interest in Android on Kovsky is very high. Are there areas where the community might be able to assist with direct hardware, financial or other contributions? So please, sound off. I'm very interested to hear about chefs/devs experiences with Android and I'm certain there are many here that would like to hear more about this port.
I just didnt know how to tell all you told here... I really want to know because I love my x1 and I love Android.. but i can"t help
i have just check out the Kovsky project from Gitorious, but still don't know how to work on it. 'cause i don't have much knowledge about develop kernel and open source, why don't we have a tutorial thread about this?
You people asking when a Android rom is coming just about every day are so funny. First of all their are still major issues that need to be worked out. Android running from haret is not even every day usable yet so what is the freakin point of expecting a rom now or asking about it? Do you guys want a rom where you phone won't even last 2-3 hours, GPS dosen't work along with the camera etc......? We need All the issues fixed before we can even be thinking about a rom. When Android from Haret is everyday usable then lets start talking about a rom. So can we please give the Devs a break about this rom nonsense and let them work in peace, when their ready to release a Android rom they will release a Android rom.
wphoenix said: i have just check out the Kovsky project from Gitorious, but still don't know how to work on it. 'cause i don't have much knowledge about develop kernel and open source, why don't we have a tutorial thread about this? Click to expand... Click to collapse would like that too, i've only been reading for some good time about the advances, and would like very much to take part in the development of the kernel, but don't really know where to start from Also, what Viper says its very true... the work is probably a long way from done, depending on how much help the dev's get, which is, from what i've seen, not much. about Toe_Cutter's comment "I wonder if some dialog on the issues surrounding an Android port/ROM might result in greater community involvement, and ultimately a stellar Android ROM for one of HTC's most beautiful smartphones" ... well, yeah, i think it could... at least i hope so. xD cool down all your heads and lets just help in every way we can ...as (ilgreco112) does xD... cheering up isn always bad hahaha ps: first post!! ... Hi!
Viper89 said: You people asking when a Android rom is coming just about every day are so funny. First of all their are still major issues that need to be worked out. Android running from haret is not even every day usable yet so what is the freakin point of expecting a rom now or asking about it? Do you guys want a rom where you phone won't even last 2-3 hours, GPS dosen't work along with the camera etc......? We need All the issues fixed before we can even be thinking about a rom. When Android from Haret is everyday usable then lets start talking about a rom. So can we please give the Devs a break about this rom nonsense and let them work in peace, when their ready to release a Android rom they will release a Android rom. Click to expand... Click to collapse As a dev, I bet it IS tiring hearing all the spectators asking about an Android ROM. But what do you expect when spectators ask about the issues, and receive nothing in response? In my original post, I chose my words very, very carefully, because if you go back and read it again, I never asked when, I only asked the why and how. Why is it that no one can provide a response to this question? I searched the forum, and read thru dozens of posts trying to understand what this port might require, and I got nada (except several polls asking about an Android ROM, and a few more posts telling the spectators to quit asking about an Android ROM). Anyone care to break the cycle and help the community understand the issues?
Well, the problem is that you can never guess what's required and how to achieve it. First of all, developers really know nothing about the hardware before they begin hacking it. Until you finish the job, you can't estimate the time it takes to complete. The major problem is that most of us devote just a tiny bit of our time to the porting, because there are lots of interesting things to learn and to do except it, but mostly because everyone's either studying or working (or even both). But if you really want to know what's needed.. well 1. Fix the LCD panel (add the initialisation code) 2. Fix the power saving (that's the greatest PITA right now) and 3D (the latter should be easy and is not really critical) 3. Implement Bluetooth, FM Radio, Camera (Should not be really hard on the driver side, but rather on the RPC protocol side) 4. Fix USB (should be easy.. actually, everything's done on the device driver side, the problem seems to be with the msm usb driver itself.. just needs real debugging) 5.Make a version of rom that boots from NAND (well, once you get the LCD to work correctly it's not a problem. It actually boots very well off nand, but without LCD and USB working it's not much fun, to tell the truth) 6.Clean up the code, drop the ****ty-droid and head forwards to SHR/Maemo MER/Meego or some other real linux distro with X11 and other things 7.Write up misc stuff (like optical joystick, illumination, new keypad driver and others) But really, it you want to help, just begin researching everything yourself and exploring wince drivers. You know, Theo de Raadt once said: "shut up and hack", and that's the only way to get things done.
full ack @sp3dev full ack your post. the main problems ar not at android 2.x this source we have. but the kernel an its's modules (for kovsky) are the problem. regards
Toe_Cutter said: As a dev, I bet it IS tiring hearing all the spectators asking about an Android ROM. But what do you expect when spectators ask about the issues, and receive nothing in response? In my original post, I chose my words very, very carefully, because if you go back and read it again, I never asked when, I only asked the why and how. Why is it that no one can provide a response to this question? I searched the forum, and read thru dozens of posts trying to understand what this port might require, and I got nada (except several polls asking about an Android ROM, and a few more posts telling the spectators to quit asking about an Android ROM). Anyone care to break the cycle and help the community understand the issues? Click to expand... Click to collapse The ROM question has been answered time and again throughout various threads on xda-dev. There is no real issue "porting" Android to kovsky. Android is a virtualized environment running on a linux kernel and it is that kernel that has to be ported. "Android" runs 100% on kovsky with minimal modification. So. There is only one issue with the linux kernel - that issue is when the linux kernel for kovsky is good enough for someone to make the effort to pack up a ROM with that kernel, a bootloader and the android system. Now, the consensus is the kernel isn't as yet good enough for daily use - if someone with the skills decides it is and makes a ROM, then they will obviously do so. The list of kernel stuff to be fixed is broadcast all over this board and asking kernel devs to repeat themselves ad nauseum won't get it done any faster
[Q] Dual boot?
I was wondering if dual booting would be possible on our phone? I've seen that the HD2 got winmo + android boot... But having some kind of Stable partition and a second "dev" one would be quite amazing... Thanks!
I asked the same question, and my post was moved to Q and A. Most responses were that WinMo is not worthy of the hardware. WP7 didn't attract quite the same disdain. I would really love to run WP7 on the captivate, and I think eventually someone will make it happen. I think WinMo would run amazingly smooth, but I doubt we'll ever find out. The HD2 won't quite run android ROMs, you have to boot into WinMo, then restart in Android, but it is really easy to swap what "ROM" you are using. If the HD2 was capable of AT&T 3G, I would have one by now. Sent from my SAMSUNG-SGH-I897 using XDA App
Yes please to WP7 on Captivate. If nothing else i want to be able to run it for a few days to see how I like that new software. And check out the Xbox Live integration
yes, i only have one phone but would like to learn to do some basic development and it would be nice to have a stable rom to switch back to on the fly. i've had problems using nandroid and titanium backup. if anyone knows of a way to change to or add a secondary boot loader so multiple os's can be launched that would be awesome. minmo might be a bit impractical but multiple android installations would be cool sweet.
Ok.. well get a checklist started on what you would need: A custom bootloader that would work with the Captivate.. And I'm sure people would want the choice to pick the OS upon bootup instead of having to go into the recovery screen and booting up from there. It would also have to be compatible with working Android and Win7 Someone would then have to find the source code to Win7 - or at least the SDK for it and develop in whatever language its written in. Then someone would have to code the drivers for the Captivate and Win7 mobile. Pretty much.. it wouldn't be any type of "take n' bake" task and would be quite the project involving a ton of work. I'm sure someone out there in the world will come up with it.. I mean someone took the time to port Android to the iPhone - so it "could" happen.. but most likely won't due to the huge amount of work it will take.
avgjoegeek said: Ok.. well get a checklist started on what you would need: A custom bootloader that would work with the Captivate.. And I'm sure people would want the choice to pick the OS upon bootup instead of having to go into the recovery screen and booting up from there. It would also have to be compatible with working Android and Win7 Someone would then have to find the source code to Win7 - or at least the SDK for it and develop in whatever language its written in. Then someone would have to code the drivers for the Captivate and Win7 mobile. Pretty much.. it wouldn't be any type of "take n' bake" task and would be quite the project involving a ton of work. I'm sure someone out there in the world will come up with it.. I mean someone took the time to port Android to the iPhone - so it "could" happen.. but most likely won't due to the huge amount of work it will take. Click to expand... Click to collapse At least there's a Samsung Omnia 7. It has a 4" SAMOLED like ours. I hope it has more in common with us as well so it would make the process easier.
JayPhill89 said: At least there's a Samsung Omnia 7. It has a 4" SAMOLED like ours. I hope it has more in common with us as well so it would make the process easier. Click to expand... Click to collapse if winmo gets ported great, if not oh well, if you read the op it was not to get winmo but just used the hd2 as an example of dual boot on a phone. a boot loader is a starting point so can the topic go in that direction? i just dont want naysayers to get confused and tell us every reason we wont get or dont want winmo.
You cannot just take the source code for WP7. It is not open source. You can port android to things, but not the other way around.
nbs11 said: You cannot just take the source code for WP7. It is not open source. You can port android to things, but not the other way around. Click to expand... Click to collapse As Dani897 said, the thread is not about porting WP7 to our phone, but just having dual boot to be able to have (lets say) one stable rom and one dev rom on the same phone...
seriously want this to happen figure it out
Noob Friendly Q and A Help Thread
I have been on the Nexus 6 since early December 2014, and for me, as with many others, the Nexus 6 was my entry point into the pure Google experience, and my simultaneous departure from TouchWiz. From the beginning, I was a noob on this device. So, after 4 short months, I have found that the rom threads have become congested with endless questions that are not germane to the given rom. The more popular a rom becomes, the problem intensifies. I can imagine how frustrating it must be for a developer whom has worked hard, flung his or her creation to the xda shadowed wilds, only to return to a thread that has become a thicket of repeated questions. Compounding the problem is that each developer has a different approach as to how he or she wishes his or her thread to be managed, which in turn can be confusing to any user. Some developers seem happy to remain ensconced in the daily comments, while others have a palpable disdain for off-topic quotes. Irrespective, I think each has a tipping point, and thus I am sure that none is immune from becoming a bit jaded after a time. And yet, we still have the very real phenomenon that this device has a learning curve, is available across the globe, and thus the questions still recur. Further, it is in many people's natures to either want to help or at least be cautious prior to rooting their device, etc. So, I thought it would be fitting to provide a place for all to ask whatever they want. As the title clearly states, this is a noob friendly place, so please feel free to ask whatever you would like about this device. I am certain that all here on these forums would rather you learn what you need prior to availing yourself of the amazing array of resources in the development and themes and apps sections of these forums. A few preliminary guidelines for this thread: This is a noob-friendly thread, so ask whatever you like Read the initial posts of the rom thread, as well as the last 10 or so pages of that thread, before you flash the rom you want. It will give you an idea of how the developer handles his or her thread, the tools you need before you get started, and Please respect your fellow forum members, developers, and the moderator staff. Moderators have a thankless job, and I can assure you that it is absolutely no fun spending hundreds of hours on what amounts to a volunteer position without benefits. Towards that end, please read the rules; they are the first post on every forum here on xda. Thank everyone that develops, and please donate to anyone whom you believe is worthy of your extra gratitude. Donations are never required, but they do motivate those that do the hard work on these forums. Never downgrade your bootloader. Ever.
I’ve split this into categories so that folks will have some basics right upfront. 1.First Use 1.1:You almost certainly will want to unlock your bootloader, inject root, recovery, etc. I suggest reading the All-in-One Beginner’s Guide, where you’ll find everything you need to get started. 1.2. Learn Fastboot: Yes, you have a Google device, and it is very easy to flash anything you want with a few simple command lines. Put bluntly, on Nexuses, the manual steps are very easy. Hie yourself to this authoritative thread written by the prolific dev and highly respected forum member @rootSU. 1.3:Toolkits: Toolkits are a fantastic way to do all of this from the jump. There's nothing wrong with toolkits themselves; they can be great, useful tools, but please learn to do the steps manually. Why? Simple. If anything goes wrong, and it can, knowledge of fastboot will save you; no knowledge of it, you're waiting on help from others, or learning from scratch that which you should already have learned. Further, should help arrive, that person helping you is bearing two burdens, helping you first learn the basics of command line, and solving your problem. That is downright unfair. OK, onto the toolkits. You can find them in the development sections, specifically: Wugfresh's Toolkit for Windows Operating System Nexus One-Click Mac Toolkit for the OSX Skipsoft Unified Android Toolkit for Windows 1.4: Decrypt or Not Decrypt: Please note: Decrypting your device will wipe your device, so if you are going to decrypt, please do so before taking all of your time to setup your device the way you like it. IF you want to remain decrypted, put the zip file located in this thread on your device, throw it in your cloud storage (Dropbox, &c), keep it in your pocket, think well of that file. IF you want to remain decrypted, that zip should be the LAST file you flash before any new rom or kernel is flashed, or if you are unsure if a rom has a kernel that will force encrypt your device. There are differing opinions as to the wisdom of decrypting, and I don’t care whether you think it is better or worse; people want to do it. You can learn more about it here, and can accomplish the task using the link previous link or using any one of the aforementioned toolkits. 1.5: Recovery: You almost certainly want to make a backup of your device prior to tweaking, flashing an updated nightly, or testing a new rom. Recovery for our device can be found here. You may want to put a nice theme on that TWRP, go here. Hint: The developer whom does those themes keeps up with each iteration of TWRP, and if a new version requires a new theme, check the theme thread before you update your recovery. 1.6: Starting Over I believe that this community owes a special thanks to @Q9Nap and @scrosler as each has provided us with amazing tools to return to stock or upgrade your device from 5.01/5.02 to 5.1, sans the need to revert to stock 5.01. Please go to http://forum.xda-developers.com/showthread.php?t=3066052 thread for flashable zips of entire 5.1 roms or modems ,or this Android File Host page from SCrosler for flashable 5.1 modems + bootloaders...https://www.androidfilehost.com/?w=files&flid=23050 https://www.androidfilehost.com/?w=files&flid=23050
2. Choosing a Rom: Roms generally fall into four discrete categories: 2.1: Stock-Based – these are hewn from Google source, and typically come preinstalled with everything you will need to be up-and-running. Whatever tweaks, performance or otherwise, are added, the rom will most certainly similar to stock, hopefully better than stock. 2.2: AOSP-Based – these are built from the Android Open Source Project, and purists may think of them as closer to what Google intended. You will typically need to flash a Google Apps (Gapps) package separately from the rom itself. Some of these have inline kernels, or stock kernels, but they typically have everything you need baked right into the mix. There is an incredible variety of unique and wonderful roms from which to choose that fall into this category. 2.3: Original Development – Although the lines tend to blur, suffice it to say that roms in Original Development contain something original that merits a rightful place of its own, away from the crowded Development Forum. You will find kernels as well as complete roms in this section. 2.4: Hybrids – The vast majority of roms fall into this category. Much of the joy of Android is customization, and most roms in this category are feature-rich and packed with things, almost more than you will ever use.
Customization - Enhancing the Senses Rom Customization: Roms are popular and highly useful, but they are also fun. Instead of using a boring, stock phone laden with what amounts to another's idea of what you should have on your device, you are in control. This starts with how the phone looks. Yes, your phone can and should look exactly how you want it. Disenthrall yourself from the madness that is a stock looking phone and apps, and stare with wonderment at beautifully themed apps. 1. Hard-Coded Themed Apps: Anyone can run a themed app, even on a stock, rooted rom. These forums are riddled with themed app threads. Some suggestions to start: 1.1: Team BlackOut, the hardest working devs on xda are there, please go into their thread, enjoy the camaraderie and the beautiful apps they make. Be sure to thank and donate if you are so inclined. You will find themed versions of scores of apps, all available for free from their updater app. 1.2: XDA Recognized Themer @cerj has done a terrific job theming many apps on his own, and of course with the help of other themers. He is a terrific resource and a good friend. Check out his Blue DeLucia and Krome-X apps. 2. Theme Engine and Layers Many Non-Stock Roms make use of one of these two basic tools that allow you to theme your entire phone. Suffice it to say that these are mutually exclusive means of attaining a beautifully themed rom without much hassle on your end. The CyanogenMod theme engine has its fans, and the fine devs doing the Layers app consider their work stellar (as they should); both are excellent. 2.1: Layers: If your ROM has Layers, and the app is not already on your phone, you'll need to download the free app from the Play Store. You'll find an abundance of themes in the Official MEGA RRO Layers Overlays Collection. Special mention to one of the finest themers whom I've come to know on these forums; as RRO has had met the steep ramp-up with stunning strides, this terrific dev has been there, every step of the way.. @daveyannihilation, a tosser, wanker, and a very Gary dude, please help...I mean thank this man. He's everything and more. Please help me, inasmuch as I'm far more concerned about the degree to which I'm both a wanker, and a tosser, not to mention completely Gary. 2.2: Theme Engine: If your rom incorporates the CyanongenMod 12.0/12.1 Theme Engine, you can find a ton of beautiful themes in the Official MEGA CM12 Theme Engine Thread. Please buy the themes you love. Free themes are terrific, but I always believe that people are more motivated to continue delivering these terrific tools if you support their hard work. Buy the damn themes, and don't be a cheapskate...there's enough whining in these forums to make most want to wretch.
Kernels and Tweaking If you wish to flash a kernel, here are a few guidelines to get you started Note: Most all of this was written entirely by @wrongway213. 1. Kernel Basics: 1.1: Stock Kernels: You can keep a stock kernel if that is with which you are comfortable. The stock kernel will force encryption, and there are modified stock kernels that will not force encryption. 1.2: Custom Kernels: 1.2.1: Hotplugging: Hotplugging is basically the background process going on telling your phone when it needs to bring CPU cores on and offline. This controls how much power your phone consumes - both how much battery it drains and how snappy it feels. You can use a kernel tweaker app (more below) to set all kinds of things in the kernel, including how hotplugging is done. Different kernels have all sorts of different hotplugging options. As of 5.1, stock kernel uses all four cores online at all times as opposed to hotplugging. This is said to save power. Some kernel developers have adopted this as the default for their custom kernels, but they are still tuned very differently than stock. The user can still choose to revert back to hotplugging if they prefer it. Prior stock kernel, including 5.0X Lollipop, use something called MP-Decision to scale your frequencies. Some are of the opinion that MP-Decision is entirely too aggressive in how it handles this. It attempts to give the user a snappy and smooth experience, but in the end it mainly drains battery. The same smooth experience can be achieved via hotplugging properly on a custom kernel, and your battery will thank you for it. 1.2.2: Governors: Another awesome thing you can do when you flash a kernel is control the governor it uses. Stock kernel uses an interactive governor, which responds to user input and is generally considered to be a pretty good governor, even for custom kernels, However, it is often modified on these kernels, or at the least assisted with hotplugging in a different way than stock. This governor has been modified by @Imoseyon for leanKernel, one of the most popular kernels for our device, and a great place to start if you want to know if custom kernels are for you or not. Some prefer to use conservative, which is much less jumpy than interactive - meaning it does not scale frequencies up or online cores as quickly as interactive. This governor has been heavily modified for our device by @franciscofranco (Franco Kernel dev), so it is a much more viable option for those whom want to conserve battery and still get great performance. There are many different governors offered with different kernels - you can change your experience on the very same kernel by changing governors sometimes. Or you may find that you flash a new kernel and find a whole new set of governors that are more your style. This is all about trial and learning what you like, as none of us can know what is best for your use. 1.3. Kernel Use and Utility: 1.3.1: Wakelocks, An Example A kernel can do many things if the kernel dev chooses to make it, or to give the user the option to avail such options, or can be omitted entirely if running stock. Though not the source of your wakelocks, kernels can disable wakelocks can control or disable them. This is a good example of the separation of a kernel's ability and a kernel's use. 1.3.2: The Domain of the Kernel: Many kernel devs choose to leave the kernel footprint small, and allow the ROM side of things to handle as much as possible. Some kernels use the existing ramdisk that comes with the ROM instead of inserting their own to ensure they will play nice with all roms. Other kernels are highly customized and completely and totally change the feel of your device. Most are somewhere in the middle of these extremes. 1.3.3: What Your Kernel Does Not Control: Your kernel does not control your radio, your WiFi, etc, so thus your phone calls, your data, your mms and sms messages are not impacted by flashing a kernel. Sometimes flashing a kernel may somehow cause something that is controlled by the ROM side of things not to work correctly - this is not the norm, though. If you are having these issues, you should look to your ROM first. 1.3.4: Random Reboots: Random reboots are something that may be caused at a kernel level. If you encounter one, you should immediately on boot (ie, right after the random reboot) open your file explorer go to the folder: sys/fs/pstore There should be an annotated-ramoops file and a dmesg file (think of these as kernel logcats). Open the files as text, copy and paste to www.hastebin.com and send the link to your kernel developer. This will help him or her determine if it the reboot was caused by the kernel, and if it can be fixed. 1.4: Sound Practices: 1.4.1. Avoid Multiple Kernel Tweaking Apps: The use of multiple kernel tweaking apps is contraindicated. If your rom comes with a performance app but you like to use your own instead, freeze your rom's performance app in (using the built-in App Manager, or with an app like Titanium Backup) and clear its app data prior to using your app of choice. Most kernels have an app that is either directly associated or supported by them, or recommended to use with them. Find this out in the thread before you tune your kernel, as having the right options available and interfaced correctly makes it much easier to do so. It's also good practice if you have flashed a custom kernel already to re-flash your rom before flashing another to ensure settings stick properly. This is not always necessary, but it only takes a minute and it's better safe than sorry. 1.4.2: Default Kernel Settings or Using Terminal Command Line: Some kernels don't even require an app at all. A few of them are tuned on initial setup via Aroma installer - you set your values and can leave it at that. Others can be tuned directly via terminal emulator. 1.4.3. Kernel Tuner of Choice: Most kernels require some sort of an app to set your values. If your kernel does not come with a particular app associated with it, there are a few options for you. A popular option has always been Trickster Mod. This app offers the basics that you need if using a kernel that does not have a whole lot of odd modifications and is good for beginners who are using a kernel with no recommended app. Advanced users often use Synapse - it is a very confusing app and definitely not for beginners, but it gives you control over basically everything your kernel has to offer. Kernel Auditor is something in the middle, as it does not allow you as much control (or confusion) as Synapse, but it can do a lot that Trickster can't. It's a great starting point for those of you using a kernel with needs Trickster does not meet, or a good place to jump to if Trickster is just getting old, but you're not ready for Synapse. 1.5: Afterwards: To be sure, there is plenty more reading to be done, depending on which kernel you choose to flash and how advanced you would like to get with it. This is just meant to give those of you who don't know why they would want to do something like flash a kernel a starting point. The decision is yours. Happy flashing!
Thanks for this man! I agree this needed to be done. It will be very helpful! Войн Дух
So... If I have a OnePlus One can I use the decrypt file you posted in the second post? I'm kind of a noob... [emoji5] In all seriousness, XDA is better for having someone like you here to help out. Watch closely people... You might learn something.
Now I just need to get one lol Awesome work buddy!
If you need more posts added in or want to transfer a post ownership to another person, just let the mod team know (or you can hit me up as well). Anything to reduce the number of non-essential, non-logcat-attaching posts from the Dev threads is most assuredly welcomed. Good job and keep up the good work.
If you're going to mention us "traditionalists" (its nothing to do with tradition) I think it only fair that you explain the reason why we dont recommend toolkits for the uninitiated @micmars, for balance
rootSU said: If you're going to mention us "traditionalists" (its nothing to do with tradition) I think it only fair that you explain the reason why we dont recommend toolkits for the uninitiated @micmars, for balance Click to expand... Click to collapse I knew you'd pounce on that. My apologies good sir. You will get one entire block in that section...please think of this as a beginning of things. Sent from my Nexus 6 using Tapatalk
micmars said: I knew you'd pounce on that. My apologies good sir. You will get one entire block in that section...please think of this as a beginning of things. Sent from my Nexus 6 using Tapatalk Click to expand... Click to collapse Yeah sorry I always do. Its nothing personal. Nothing to apologise for. I just think a little disclaimer could be put in. I can draft a very small sentence if you like... Or not
Excellent idea, this thread is, Mic - thanks for endeavoring to provide a one-stop-shop resource for all. Let me know if I can be of any assistance along the way.
Very useful thread. Will be checking in to help whenever I can. Thanks @ micmars TaPpEd FrOm My N-sIx
rootSU said: If you're going to mention us "traditionalists" (its nothing to do with tradition) I think it only fair that you explain the reason why we dont recommend toolkits for the uninitiated @micmars, for balance Click to expand... Click to collapse Toolkits, like a decrypted device, are a double edged sword. I have been screwed over by tool kits in the past but I've also been saved from doing something stupid. I do like tool kits that include a command line option and are verbose enough to show you exactly what they're doing. My $. 02 I do have a newbie question though. This is my first device without SD card. In the past I was never gun shy about doing anything because I knew worst case I could recover or at least have my install zips and titanium backup to rebuild . Now a days I am sometimes scared to wipe my pseudo SDcard. What are you folks doing to protect yourself? I have been saving off data to the PC before anything major but it seems like there should be a better way. Sent from my Google N6 on VZ
DebianDog said: Toolkits, like a decrypted device, are a double edged sword. I have been screwed over by tool kits in the past but I've also been saved from doing something stupid. I do like tool kits that include a command line option and are verbose enough to show you exactly what they're doing. My $. 02 Click to expand... Click to collapse Yeah i agree. That's why it should be a disclaimer rather than an order DebianDog said: I do have a newbie question though. This is my first device without SD card. In the past I was never gun shy about doing anything because I knew worst case I could recover or at least have my install zips and titanium backup to rebuild . Now a days I am sometimes scared to wipe my pseudo SDcard. What are you folks doing to protect yourself? I have been saving off data to the PC before anything major but it seems like there should be a better way. Sent from my Google N6 on VZ Click to expand... Click to collapse I use folder sync as a plug in to Tasker. Every time I close my camera app, I use bash shell to look for new files in DCIM and move them to a holding location. I then use folder sync under the same trigger, to open up an SFTP connection to my NAS at home and upload the photos immediately. There is one draw back though. I was taking 4k videos the other day and trying to push 1.5GB over sftp voa hspa is not good for battery, so I need to revise that one. Also a run a times folder sync every couple of days syncing up my /sdcard with my NAS backup directory, over WiFi whilst I sleep. Also every Saturday at 3am, my phone reboots, takes a nandroid then syn a that to my NAS too. As you can imagine, I find it difficult to lose files
DebianDog said: What are you folks doing to protect yourself? I have been saving off data to the PC before anything major but it seems like there should be a better way Click to expand... Click to collapse Same here. Only takes a minute.
DebianDog said: Toolkits, like a decrypted device, are a double edged sword. I have been screwed over by tool kits in the past but I've also been saved from doing something stupid. I do like tool kits that include a command line option and are verbose enough to show you exactly what they're doing. My $. 02 I do have a newbie question though. This is my first device without SD card. In the past I was never gun shy about doing anything because I knew worst case I could recover or at least have my install zips and titanium backup to rebuild . Now a days I am sometimes scared to wipe my pseudo SDcard. What are you folks doing to protect yourself? I have been saving off data to the PC before anything major but it seems like there should be a better way. Sent from my Google N6 on VZ Click to expand... Click to collapse On the go storage, tiny little things, I know many themers, and rom devs, use the crap out if them. I have seen these things sold at very reasonable prices, at brick-and-mortar retailers or online. I personally back up my entire card to my computer on a weekly basis, and throw the entire thing into my Dropbox. Sent from my Nexus 6 using Tapatalk
Let me start by saying thank you.. I recently purchased evo 3D, then flashed a nexus 6 ROM and recovery.. My question is, should my phone be this hot.. It's lethal it's so hot.. I'll wait for your trusted response.. Seriously, for all that know mic, he is a beacon of knowledge.. This thread will not only widen your vocabulary , it will contain a plethora of information and innuendo
cerj said: Let me start by saying thank you.. I recently purchased evo 3D, then flashed a nexus 6 ROM and recovery.. My question is, should my phone be this hot.. It's lethal it's so hot.. I'll wait for your trusted response.. Seriously, for all that know mic, he is a beacon of knowledge.. This thread will not only widen your vocabulary , it will contain a plethora of information and innuendo Click to expand... Click to collapse your phones cpu can get to 100C. thats when itll automatically shut down/reboot to cool off. but try as hard as you can, i bet youll never reach it. anything below is normal, depending what you are doing. now you say hot, whats your cpu temp? as feel does not give you any temperature. all feel does is tell you if something is hotter than or cooler than your hand. and if your hand is cooler, itll make the phone feel much hotter. so, when talking about being too hot, we need an actual temp to go with it. i say that because many people report a hot device, when the temp is around 40C, when normal body temps average around 37C.