Hi all, hoping you can help me out with this. It's not a critical issue, more a vanity/QOL thing.
I'd like to change the device name/ID that shows up when connecting my Nexus 7 to a wifi network. Currently it shows up as "android-<string of alphanumerics>" but I'd like to be able to give it a more descriptive name to help differentiate when setting up a wifi connection around multiple similar devices.
I've got my N7 rooted but not unlocked, and I'd prefer not to flash a custom ROM if possible. I'm no stranger to flashing ROMs, I'm just not interested in putting a huge amount of work or potentially causing myself problems for something that is so relatively minor.. I can live without a custom device name, but it would be nice to be able to set one up.
Thanks in advance!
{
"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"
}
Is that screenshot from the custom ROM you have listed in your sig?
I'm using a stock N7 with build JDQ39 and I don't seem to have many of those options listed in the Developer Options menu. Or is there something I need to do to enable those, similar to the method used to 'unhide' the Developer Options in the first place?
My apologies if this is basic information that I could have found elsewhere.
TechDragon said:
Is that screenshot from the custom ROM you have listed in your sig?
I'm using a stock N7 with build JDQ39 and I don't seem to have many of those options listed in the Developer Options menu. Or is there something I need to do to enable those, similar to the method used to 'unhide' the Developer Options in the first place?
My apologies if this is basic information that I could have found elsewhere.
Click to expand...
Click to collapse
Yes it is Slim Bean Build 7. That is just what I use as it is included in the ROM. You can set it manually or use an app such as these.
Wow.. I feel incredibly dumb right now. I'm so used to doing things the hard way I didn't even consider checking if there were apps in the store that might do what I wanted. Thanks for reminding me to look in the easy places first!
Cheers!
Related
I am assuming once you root the phone and push a custom ROM onto the phone, this will fix HTC's introduced bugs?
Bluetooth
SMS battery drain
Reverting apps versions
Stuff like this.
No, because the custom ROM is just the Sprint ROM with a few additions and modifications.
Ouch.
ok, anyone working on compiling a 2.0 kernal?
Treefallingquietly said:
Ouch.
ok, anyone working on compiling a 2.0 kernal?
Click to expand...
Click to collapse
HTC
{
"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"
}
Although the bugs are not fixed, rooting allow one to use various workarounds that would not be possible without, and in fact for EACH of the issues you have listed:
Bluetooth: http://community.sprint.com/baw/thread/23854?tstart=0
While I cannot personally vouge for this, I have seen many posts on Sprint and here that detail the workaround described in the post as effective.
SMS Battery Drain: I think this may have actually been the first big bug discovered, and also fixed without root! Unfortunately, the default messaging app is defective, so in the meantime it is recommended to use either chompSMS or Handcent SMS from the Market until an update is released.
See this post: http://community.sprint.com/baw/thread/23043
Finally...
Reverting Apps: This is addressed on both forums, but a workaround only exists with root, and is similar in fashion to the bluetooth fix but for a different directory.
http://forum.xda-developers.com/showthread.php?t=582176
http://forum.xda-developers.com/showthread.php?t=581806
Hope this helps! I intend on posting a very detailed guide on every step of rooting, backing up, and working around most of the detailed problems in the very near future, stay tuned!
What I'd like is a kernel that will have this working as intended. But really, I am not afraid of the work arounds and the hands on work required, but if my wife had this phone with these problems, she would have chucked it out the window within days.
One more...
You left out the original bug (mentioned by briankwest, one of the first rooters), the TCP timestamp issue:
echo 0 > /proc/sys/net/ipv4/tcp_timestamps
This could also be added to the MoDaCo init.rc so it is set at each boot (otherwise it will revert back to "1").
OK, I'm trying to unlock a Vibrant for someone else. I have read and tried several methods with no success yet.
I had Axura 2.2 and tired the SGSUnlock with no luck
I ODIN'd back to stock20100512.pit / t959UVJFD.tar and SGSUnlock still doesn't work. Ive tried two variants of it, nothing.
I have limited experience with ADB (driver issues between multiple devices so I use ADBWireless) and was able to get an nv_data.bak and used a hex gen to get this (screenshot).
{
"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"
}
According to notes, I'm to find the code separated by periods, but I have no periods. Anyone have an idea or can lead me to a quick fix?
Remaining questions, once I generate a code, will the code I use at stock 2.1 work once I flash 2.2 back on?
Thanks for any help or guidance, much appreciated!
anyone? Bump?
You're out of luck as far as SGS Unlock goes. Any ROM update JI6 or later corrupts the code in the nv_data.bin file. There is this method thanks to helroz that has worked though.
http://forum.xda-developers.com/showthread.php?t=822008&page=4
thanks for that... Seems like work Will an unlock code from TMO still work outright?
it2steve said:
thanks for that... Seems like work Will an unlock code from TMO still work outright?
Click to expand...
Click to collapse
If you use this method I don't think so since it changes the actual code. You could always call TMO and get the code instead of doing it this way as well. Think it usually takes a few days.
If you need a unlock. Hit me up. No matter the rom. no matter the lock.
Same here. I need to unlock a vibrant I just got.
djidea said:
Same here. I need to unlock a vibrant I just got.
Click to expand...
Click to collapse
If you just got it then you are still on 2.1? Just search the market for "SGS Unlock", that'll do it.
If some developers could try and add their ROM's to test this out that would be a big help.
http://roms.scottymeuk.co.uk
Features
Add Device
Add ROM to Device
Add Version (Release) to ROM
Changelog
Comment System
Like/Dislikes
http://roms.scottymeuk.co.uk
This is probably been attempted before but I got bored and decided to make a ROM Directory type thing. It took me a day to develop and is written in PHP using the CakePHP framework for anyone that is interested.
If anyone has any feedback or anything please let me know.
The reason there is only 1 ROM added is because they are the files i have on my PC as i use that ROM.
Below are some pictures of it:
http://roms.scottymeuk.co.uk
Add Device
{
"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"
}
Add ROM Version
Device Home
Device Page
Login
ROM Page
Submit ROM
Change Log (Per Version)
http://roms.scottymeuk.co.uk
Very nice set up I would definitely use it. Ive been doing alot of work lately on my friends and family's android phones and if you can get this up it wont take forever to find a rom that they like and i can set it up for them
http://roms.scottymeuk.co.uk
It would definitely be nice to have one stop place for all the latest ROMs. But, in my opinion creating the website isn't the hard part, the hard part is to keep your directory updated with the latest ROMs.
Because there are lots of ROMs available (different phones, different versions etc) and many people use nightly builds too like in case of Cyanogen. So, that would mean you will have to update the data/urls/change logs etc regularly.
How do you plan to aggregate and update all this data? Manually? Or fetch data as a feed from their respective website? Or hoping for the web 2.0 way?
But, if you manage to do that then it would be really great.
People who create the ROM's will be able to do all of that them self. The way it works is that the ROM is submitted by someone (doesn't have to be the developer) and then that ROM is locked to their account, it is then approved by an admin and then they are then free to add as many versions as they want, where they can upload a zip file, and add change log for THAT version.
The change log is not one big database entry, it is the "versions" of the roms. For each version you submit there is a change log.
Hi,
I want to install Android on my HTC Touch pro. Now I've done a bit of research but I still ain't sure.
I Live in Malta, and bought an unlocked phone from the UK (eBay). I downloaded the XDAndroid thing from the XDAndroid Wiki but I don't know which is my exact model. I went with the RAPH800, and when I ran it, it seemed to get stuck on the booting. it said something about a bug :S I only could pull off the battery, as nothing else would work.
So, Im back to step one.
1. Which exactly is my phone model?
2. If it was the RAPH800, does it normally get stuck on 'bug KENDEL' something like that
3. How long does the booting take overall?
major props to any1 who helps me
EDIT: I also wanna do the Dual-Boot thing using using GenY-DualBOOT (got it from this website). Any1 can help me doing that, and if its worth it or no
Thanks guys.
P.S. I'm a noob, so I need very detailed instructions
OK, I have a new problem. i downloaded another installer, and it didn't crash. (There was a default SETUP.txt file so I used that. I'm getting to the XDAndroid screen, but then some grainy aindroid toolbar comes, my phone vibrates, and stops there :S
Any ideas (pics to follow soon)
Pics are huge, like 2MB each, and it doesnt let me post from tinypic before 7 posts -.- Hopefully you know what I mean
{
"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"
}
As you can see, 3rd and 4th is where the problem arises. The other 2 are just there so you see what comes in the meantime.
(huge pics are huge)
Last BUMP. If I don't get helped, I'll just give up
look
View attachment 582719look
This might not be the right section to post this in. I would suggest going to the android development section for your specific phone.
HI all,
I'm looking to flash my phone with a newer ROM. I'm currently on one I installed quite a while ago. I'm now a bit confused on which ROMs I can and can't use.
My phone is MF9 according to what I've been able to locate in the about settings and phone info programs. I keep seeing stuff about OD2, but I'm not really sure what that means for me. Also, isn't there something about updating and it doing something to the boot loader?
Do I need to update to OD2 to use newer ROMs?
Will it lock my boot loader and what will that do to my ability to change ROMs later?
Lastly, and I know it's a matter of personal preference, what ROM would you recommend? I'm just looking for something stable. Though good battery life and fast would be nice too.
Thanks,
-Jeff
OD2 didn't lock my bootloader. The updated bootloader actually means you'll be free to use more recent custom ROMs.
As for ROM recommendation, usually it should be a no-brainer for me to give CM, but CM on this phone drains battery a bit too fast, so I'll hold back on that.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Thanks Andy,
So, if I do an Odin update to OD2, I should still be safe on my phone? That takes a load off my mind.
I did CM back on my Nexus S4G years before I got this phone. It wasn't bad. The battery life thing is a deal breaker though. Now that I know I can safely update without screwing things up too much I'll play around with a few. My main thing is to update my wife's phone so that she doesn't have problems. She always insists on matching phones so I can help her with stuff LOL
-Jeff
Only AT&T and Verizon lock bootloaders, you could try my ROM, Wicked X, in the Android Development section. Very stable and battery friendly.
{
"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"
}