Related
I odexed the mod..
Someone with a stock odexed rom.. please try and report back
Push framework.jar and framework.odex to system/framework via adb
or.. use root explorer. Make sure to give proper permissions, reboot into recovery
and clear cache and dalvik and then reboot
just start your hotspot and test! Mine works perfect.. feedback please..
Please report results
Paste Bin of my work
http://pastebin.com/T1XieFt9
Is this just the hotspot hack or the nociq+hotspot hack?
Is this the same as the original thread or did you redo the hotspot hack to be minimal? I believe people mentioned the other one had some UI changes with scrolling.
sfhub said:
Is this just the hotspot hack or the nociq+hotspot hack?
Is this the same as the original thread or did you redo the hotspot hack to be minimal? I believe people mentioned the other one had some UI changes with scrolling.
Click to expand...
Click to collapse
This is only the hotspock hack
I am working on combining both into one odexed mod and I am just trying to get it completely right this time.
Combine this with no ciq, crt animation, and battery percentage and you will become my favorite dev
Sent from my SPH-D710 using xda premium
Hotspot is working great but I think I might be having issues with browser scrolling..
I think people were mentioned something about the scrolling with the original deodexed implementation. They mentioned going to the framework.jar in the nociq version to get rid of that problem.
sfhub said:
I think people were mentioned something about the scrolling with the original deodexed implementation. They mentioned going to the framework.jar in the nociq version to get rid of that problem.
Click to expand...
Click to collapse
This will fix the browser scroll lag but you'll end up with overscroll effect that im not too fond of. I would love to go back to stock kernel and use this odexed hack if the
framework.jar is updated with the fixed browser scrolling.
I'd like to see just the hotspot change with no other ramifications in odex'd form.
Also the other 1x/3g notification bar change in odex'd form.
Same for me, Hotspot works great but I have the browser lag, and not sure if it matters, but I moved back to my original framework.jar (to see if it made a difference) and the Hotspot still works fine.
fnut6969 said:
Same for me, Hotspot works great but I have the browser lag, and not sure if it matters, but I moved back to my original framework.jar (to see if it made a difference) and the Hotspot still works fine.
Click to expand...
Click to collapse
I am going to try that. My odexed rom has a custom theme, hotspots, nociq, and 1x/3x
Edit.. tried going back to original jar.. still have the browser lag.. going back to original odex now too
Sent from my SPH-D710 using Tapatalk
Is this 3g only?
yes
10charlimit
I still seem to be getting browser lag (un bearable lag) even after replacing the framework.jar (with the noCIQ version, by reflashing and I have tried manual copy), wiping cache and dalvik cache, and fixing permissions.
Is that normal? If this isn't, how do I fix it? I made a nandroid before I did this, so I can go back freely, but I would really like the ability to use Sprint's hotspot application.
GH0 said:
I still seem to be getting browser lag (un bearable lag) even after replacing the framework.jar (with the noCIQ version, by reflashing and I have tried manual copy), wiping cache and dalvik cache, and fixing permissions.
Is that normal? If this isn't, how do I fix it? I made a nandroid before I did this, so I can go back freely, but I would really like the ability to use Sprint's hotspot application.
Click to expand...
Click to collapse
This happened on the OG Epic when either ROM or mod wasn't done with most current baksmili. I only know this because necrosan was here when he fixed it
Sent from my Nexus S 4G using Tapatalk
JohnCorleone said:
This happened on the OG Epic when either ROM or mod wasn't done with most current baksmili. I only know this because necrosan was here when he fixed it
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
So, how would I go about fixing it, or can I fix it?
Right now, I have three versions of the framework in my phones sd card and I am going to be trying them.
I did try something though, I went back to my nandroid backup, and replaced just the .odex file as I had already flashed the NoCIQ mod and if I left the framework.jar file untouched, I would still experience the browser lag. So is this problem really isolated to the .jar file?
JohnCorleone said:
This happened on the OG Epic when either ROM or mod wasn't done with most current baksmili. I only know this because necrosan was here when he fixed it
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
John did necro fix the hotspot hack dealing with the browser lag?
I will would love to have infrastructure vice ad-hoc.
Hm, having tried all three (original in the odex'ed zip, the NoCIQ framework.jar, and the NoCIQ_HSH framework.jar) none of them made a difference. It definitely is only applicable to the .odex file. How is the odex file being edited?
GH0 said:
Hm, having tried all three (original in the odex'ed zip, the NoCIQ framework.jar, and the NoCIQ_HSH framework.jar) none of them made a difference. It definitely is only applicable to the .odex file. How is the odex file being edited?
Click to expand...
Click to collapse
Thanks GH for looking into this again and trying to fix the issue, it had died due to the browser lag.
Yeah no problem. I found out another issue that I was having trouble narrowing down too.
But, I am far from any dev, and I am not experienced in Java (or any programming for that matter), so it still will need to get fixed by someone else.
It would help if I understood what the .odex file was doing, and maybe I could poke around in it.
EDIT:
Also, forgot to mention this. I noticed that the scroll lag in the browser wasn't immediately evident. It would only take affect after the page was fully loaded, or after the checkerbox screen had showed up. This might not be accurate, but I noticed it would take affect after that.
yea this stuff is way over my head also, i was thinking as metalhead stated in his thread about strongsteve odex rom and getting the framework from there and testing or seeing what is the difference.
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Try flashing the stock tar in odin if nothing else works.
DroidGnome said:
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Click to expand...
Click to collapse
Just flash the stock tar ur downloading in Odin. Ur fine even if you managed to Bork recovery as long as u can still get into dl mode ur ok
I've haven't seen this problem on the Sprint variant yet but it definitly sounds like it's fixable
Like others have pointed out, since you can get into Download mode fine flash the Stock Odin tar file found here
When you boot up I would consider doing a data wipe (Factory Reset option in Settings>Back up and reset) but that's up to you
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
Ya Ive seen some build.prop changes mess things up. Luckily you could get back up.
Fun feeling huh! lol
fergie716 said:
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
DroidGnome said:
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
Click to expand...
Click to collapse
Glad to hear you're up and running again!!
Best excuse ever to Sprint is when I woke up it was like that haha
hi guys, as title says, will any custom roms allow bell mobility TV to work? im just curious, on my older phone that i put CM9 onto i could not get bell mobility tv to work, it would say it stopped working, even after 30 different builds,
is this the same case here? or does it work? Thanks!
I just tried mine running task650 aokp and after the app opens it tells me that my device is not supported. But, maybe I'll try changing my build.prop so that it reflects a Bell Canada phone and not an American AT&T phone.....might work....I'll have to get back to you.
I tough maybe the app was not compatible jelly bean yet?
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
patthe said:
I tough maybe the app was not compatible jelly bean yet?
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
That is also possible....may not work until we get the holy Jellybean update. Going to be tomorrow night before I get back to my computer to get at my backed up original build.prop to compare device ids and stuff.
jethro650 said:
That is also possible....may not work until we get the holy Jellybean update. Going to be tomorrow night before I get back to my computer to get at my backed up original build.prop to compare device ids and stuff.
Click to expand...
Click to collapse
ok good to know, and rom wise what is a good rom to run right now? i notice there is jellybean roms and cm10 rom, well cm10 is jelly bean i know that but whats the differences? i know my old phone, all roms where gingerbread and cm9 was ics, so of course you'd go cm9 if you wanted ics because its your only choice
and not sure device id wise, but i got this for you if it might help, kernel version 3.0.8-20120814.100513-user and build number of imm76d.i747mvlalh1
patthe said:
I tough maybe the app was not compatible jelly bean yet?
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
The App is Jelly Bean compatible, as I am using it on the latest leak. I have tried to flash Bell's csc on top of other ROMs in the past and have had no luck getting Mobile Tv to work. This includes AOKP CM10 and stock ROMs from other countries. On my S2 as well. Maybe there is something in Build.prop, but I haven't been able to figure anything out.
BCSC said:
The App is Jelly Bean compatible, as I am using it on the latest leak. I have tried to flash Bell's csc on top of other ROMs in the past and have had no luck getting Mobile Tv to work. This includes AOKP CM10 and stock ROMs from other countries. On my S2 as well. Maybe there is something in Build.prop, but I haven't been able to figure anything out.
Click to expand...
Click to collapse
where do i find this leak? , i kinda want for some reason to keep being able to use mobile tv, i gave it up before but now with this phone being faster and just better than my old, i wouldnt mind to have the ability to watch some tv when i bored lol
update: i found the leak, put er on my phone too, yay jelly bean, so what is the difference or advantages of running say CM10 vs this jellybean update from bell? thanks
Octanee said:
where do i find this leak? , i kinda want for some reason to keep being able to use mobile tv, i gave it up before but now with this phone being faster and just better than my old, i wouldnt mind to have the ability to watch some tv when i bored lol
update: i found the leak, put er on my phone too, yay jelly bean, so what is the difference or advantages of running say CM10 vs this jellybean update from bell? thanks
Click to expand...
Click to collapse
The Bell leak is somewhat buggy, but not enough to keep me from using it as a daily. The reason I use it over CM10 is simply because I love Touchwiz. CM10 seems way faster and loads of other benefit, but I think that Samsung has done really well with this as stock. If you don't stay stock, the Bell TV app will not work (to the best of my experience). It all comes down to what you like and what you want to work.
Octanee said:
hi guys, as title says, will any custom roms allow bell mobility TV to work? im just curious, on my older phone that i put CM9 onto i could not get bell mobility tv to work, it would say it stopped working, even after 30 different builds,
is this the same case here? or does it work? Thanks!
Click to expand...
Click to collapse
I got it to work by using these settings in build.prop
- ro.product.name=d2vl
- ro.product.device=d2can
- ro.product.model=SGH-I747M
- ro.build.product=d2can
works so far without issues
kvpxray said:
I got it to work by using these settings in build.prop
- ro.product.name=d2vl
- ro.product.device=d2can
- ro.product.model=SGH-I747M
- ro.build.product=d2can
works so far without issues
Click to expand...
Click to collapse
interesting, i have not personally used or edited roms or files as such, how would i go about that more specifically? decompile a rom and put that into the .prop or open .prop in notepad or what lol
i am a technical computer guy but when it comes to androids and such and their builds, i know how to root, and flash and all that dealio just not about their filesystem structure, etc,
Octanee said:
interesting, i have not personally used or edited roms or files as such, how would i go about that more specifically? decompile a rom and put that into the .prop or open .prop in notepad or what lol
i am a technical computer guy but when it comes to androids and such and their builds, i know how to root, and flash and all that dealio just not about their filesystem structure, etc,
Click to expand...
Click to collapse
Download ES File Explorer, and under settings make sure: Root explorer, up to root and mount file system are checked.
Go into the /System/ Directory and you'll see the build.prop file in there, press and hold to bring up the menu and open as a text file, and you should see the settings in there that you can change
kvpxray said:
Download ES File Explorer, and under settings make sure: Root explorer, up to root and mount file system are checked.
Go into the /System/ Directory and you'll see the build.prop file in there, press and hold to bring up the menu and open as a text file, and you should see the settings in there that you can change
Click to expand...
Click to collapse
so this is a sure fire way to get mobile tv to work?, if so then i'd go to CM10 or something if its worth it vs bells jellybean,
also if i root and put cm10 on, can i undo it all and unroot, etc so that if i had to get the phone fixed they would never know it happened? or is there some special internal sucker that knows that youve went custom and doesnt revert back that the factory checks?
sorry i suck at explaining some times but i hope that worked LOL
Octanee said:
so this is a sure fire way to get mobile tv to work?, if so then i'd go to CM10 or something if its worth it vs bells jellybean,
also if i root and put cm10 on, can i undo it all and unroot, etc so that if i had to get the phone fixed they would never know it happened? or is there some special internal sucker that knows that youve went custom and doesnt revert back that the factory checks?
sorry i suck at explaining some times but i hope that worked LOL
Click to expand...
Click to collapse
Haha, I think i got it. Yup, so far so good on my phone running CM10, in fact I'm using it right now! hahah.
There's a thread under the development section that tells you how to root without tripping the counter so that no one will know that you've rooted. And I believe that all you have to do to unroot is to flash an original stock rom
Please read forum rules before posting
Questions go in Q&A
Thread moved
FNM
kvpxray said:
I got it to work by using these settings in build.prop
- ro.product.name=d2vl
- ro.product.device=d2can
- ro.product.model=SGH-I747M
- ro.build.product=d2can
works so far without issues
Click to expand...
Click to collapse
This works for me also running task650's jellybean aokp.
I just edited this file, but I am still greeted with, "Coming to your device soon!"
Wiped app data with Titanium; rebooted as well.
I see this issue is current.
Any suggestions?
Edit: I am on 10/04 nightly
Sent from my SGH-I747 using xda app-developers app
otoolerc said:
I just edited this file, but I am still greeted with, "Coming to your device soon!"
Wiped app data with Titanium; rebooted as well.
I see this issue is current.
Any suggestions?
Edit: I am on 10/04 nightly
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Did you reboot after making the changes? I got the exact same message when opening the app. Made the changes and rebooted and started watching TV.
Beautiful, sir.
For the record: I had restarted, initially, but when it didn't work and I went back to the file to review the text once again, I realised I forgot to stick that capital M in there. I changed it, saved it, but still no tv - simply because, I didn't restart again.
Cheers bud.
Sent from my SGH-I747M using xda app-developers app
I'm curious if anyone has got this working with Rogers Live TV. I have edited my build.prop to reflect what has been posted in this thread to no avail. I am running the latest AOKP. I have even taken editing the build.prop as far as modifying the description and fingerprint.
The ro. product.name may be different for Rogers. The rest should be the same. After editing make sure you save the edited file. Hopefully you have a nandroid in case changing something here makes your phone non-booting. After saving the edited file reboot, if that doesn't work reboot recovery wipe cache/dalvic/fix permissions and try that. If none of that works you may have to get a Rogers stock ROM and see what those four lines are on stock and change them to reflect that.
BTW- which app are you using to edit the build.prop?
Ok. I am really upset with Tmo for blocking Wallet. I used it ALL THE TIME on my Nexus S on AT&T and I LOVED it. I've been trying to get it installed since October when I bought the phone and I cannot for the life of me get it to work. Everything I try fails or screws up the phone and I have to re-flash, so I eventually just said screw it and went to AOKP because I felt like trying something new. My friend said that I would be able to just install wallet once I did, but that is not the case. the install fails when using an apk, wallet is hidden in the market, and once when I got it installed it says "not available on your device/carrier blah blah blah" and quits. So, what I want is a solution. I need to know how to make this work because I am starting to get really upset. No solutions I can find work, nothing I've tried is successful... I might just be doing it wrong or missing something but I am determined to get it to work. NFC is working fine, I used it several times already.
Phone info:
Model: SGH-T999
Android Version: 4.1.2
Baseband: T999UVDLJA
Kernel: 3.0.48-cyanogenmod-faux123-att-tmo-00041-ga2c7267
AOKP Version: aokp_d2tmo_jb_milestone1
Build: aokp_d2tmo_userdebug 4.1.2 JZ054K eng.sethyx.20121029.025840 test-keys
I only did this for Stock rooted, but I think on you only need to modify build.prop and install like normal - if you want to change the build.prop back, you have to use the Modaco modified wallet apk. I think. I don't know, I just remember it being discussed in the thread that went over how to do it on stock.
If you want to use stock, there's a thread that will walk you through it on these forums, it's like, only one more step.
Pennycake said:
I only did this for Stock rooted, but I think on you only need to modify build.prop and install like normal - if you want to change the build.prop back, you have to use the Modaco modified wallet apk. I think. I don't know, I just remember it being discussed in the thread that went over how to do it on stock.
If you want to use stock, there's a thread that will walk you through it on these forums, it's like, only one more step.
Click to expand...
Click to collapse
I tried that the first time and it caused a failure to boot. second time, it was a program that was supposed to do it for me - same result.
If you're using the Touchwiz fix (which I think is what you're talking about in the "do it for you" program bit -that will brick it since it's for TW ROMs only and not needed for/compatible with your ROM.
Did you do that or follow a different thread? If he latter, it might help to post in there or at least link to it here so people can see exactly what you did.
Sent from my SGH-T999 using xda app-developers app
Pennycake said:
If you're using the Touchwiz fix (which I think is what you're talking about in the "do it for you" program bit -that will brick it since it's for TW ROMs only and not needed for/compatible with your ROM.
Did you do that or follow a different thread? If he latter, it might help to post in there or at least link to it here so people can see exactly what you did.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
up until now I was using touchwiz. I screwed up the phone both times while using touchwiz. Now, I'm on AOKP and cannot find anything that works for that - everything seems like it's for touchwiz. What I tried was flashing wallet now on aokp, and it didn't harm the phone but the program will not work. If I load it, it just says "Unfortunately, Google Wallet is not yet available for your device or mobile network." and I want to know how to get around that on aokp, ignore touchwiz, I was just mentioning that because I ditched it in part due to the problems it had with wallet.
Like I said, I think you need to modify the build.prop just like before for the Wallet apk to install.
In the TW wallet thread, someone kept bricking their phone because they had a non-TW ROM and it was explained to them what to do instead. I would look there and read through until you find it.
Sent from my SGH-T999 using xda app-developers app
There is a thread in the themes and apps section that does this automatically for you. You install the apk, you choose your ROM, phone an carrier and then it reboots, installs the all and a lot you need to do is open the wallet and activate your card. Then go back to the original installer app and revert your build.prop. it does everything for you almost. Check it out
Sent from my Rooted Gameboy
Pennycake said:
Like I said, I think you need to modify the build.prop just like before for the Wallet apk to install.
In the TW wallet thread, someone kept bricking their phone because they had a non-TW ROM and it was explained to them what to do instead. I would look there and read through until you find it.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Ok ok, I think I understand you now. You still have to mod build.prop even on aokp? just don't have to do all that other stuff that you do have to do for touchwiz?
osmosizzz said:
There is a thread in the themes and apps section that does this automatically for you. You install the apk, you choose your ROM, phone an carrier and then it reboots, installs the all and a lot you need to do is open the wallet and activate your card. Then go back to the original installer app and revert your build.prop. it does everything for you almost. Check it out
Sent from my Rooted Gameboy
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2044362&highlight=wallet This thread?
I was using this exact app that it screwed up my touchwiz last time, and now it does not show an option for AOKP, just AOSP. Will the AOSP work?
Ok seriously. I didn't even run the app this time I just opened it and it screwed up my rom! God, why is this so infuriating! If someone had told me I would have to go through all this bull**** to get my stupid phone to work as well as my old, slow nexus s I would never have upgraded! BRB, time to reflash aokp.
*seeths with rage*
It was the thread about the by-hand fix for Jelly Bean.
I'd do it by hand just so you know exactly what you're doing so that you can troubleshoot if it goes wrong.
Are you rooted? I did this on the root66 root-injected ROM. I did find that you really need to check to make sure your build.prop has been properly edited - at first I was using an editor that just didn't work for whatever reason and wasn't saving the file.
This was the reason I rooted my phone and it worked great - so I'm sure you'll be able to figure out what is going g wrong and get it to work.
Sent from my SGH-T999 using xda app-developers app
Pennycake said:
It was the thread about the by-hand fix for Jelly Bean.
I'd do it by hand just so you know exactly what you're doing so that you can troubleshoot if it goes wrong.
Are you rooted? I did this on the root66 root-injected ROM. I did find that you really need to check to make sure your build.prop has been properly edited - at first I was using an editor that just didn't work for whatever reason and wasn't saving the file.
This was the reason I rooted my phone and it worked great - so I'm sure you'll be able to figure out what is going g wrong and get it to work.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
IF I'm not mistaken aokp is rooted by default. Anyways, I'm in the process of reinstalling it... again.
Pennycake said:
It was the thread about the by-hand fix for Jelly Bean.
I'd do it by hand just so you know exactly what you're doing so that you can troubleshoot if it goes wrong.
Are you rooted? I did this on the root66 root-injected ROM. I did find that you really need to check to make sure your build.prop has been properly edited - at first I was using an editor that just didn't work for whatever reason and wasn't saving the file.
This was the reason I rooted my phone and it worked great - so I'm sure you'll be able to figure out what is going g wrong and get it to work.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
used an app from the market to edit my build.prop and it works perfectly now. Thanks!
Rooted Maguro:
Manually changed density from 320 to 280 and now I can't get passed the Google logo when booting Can anyone help me understand what happened? Is it because I chose 280? Should I have chosen 240/241 instead?
Shouldn't have happened at all. Maybe you accidentally touches other lines. Dirty flash your current ROM and try again (you won't lose data)
Sent from Samsung Galaxy Nexus @ CM10.2
AndyYan said:
... try again (you won't lose data)
Click to expand...
Click to collapse
Kind of spooked me... have to rebuild courage before I try again
I used ROM Toolbox Lite to edit the build.prop. Pretty sure I didn't touch anything else.
kroogar said:
Kind of spooked me... have to rebuild courage before I try again
I used ROM Toolbox Lite to edit the build.prop. Pretty sure I didn't touch anything else.
Click to expand...
Click to collapse
Must be a ROM Toolbox problem then (I've seen a lot of misc problems caused by it, namely bootanimation and build.prop edits). Edit with Root Explorer or any other "straightforward" text editor.
Sent from Samsung Galaxy Nexus @ CM10.2