Hi,
For those who don't fear to brick their phone, you can try this custom rom (v11) I've just made
As of now, nothing special with it, I just added Pim Backup, only to test the kitchen, so really no reason to flash it except to confirm whether it works or not. If you want to test it, use the stock rom in this thread (thanks Dark9781) to extract the files into programsdata\LGMOBILEAX folder and then replace phone\GW820-V10d-OCT-27-2009+0.dz with mine (giving it the same name).
Once again, I can't insist enough on the fact that this is experimental for now (for this test rom, I did some rebuild stuff manually, I don't know if it works). Once the tools are proved to be stable, I'll release a updated kitchen for you to play (it might take a week or so to finalize the tools, maybe less).
if u can free up rom and ram i will like to test for u. i hate only having 70% free on reset opera 10 crashes on my phone
Downloading it now. I will post to let you know if it works after I flash it.
Just tried to flash the test rom, but it keeps causing the flasher program to crash before 4%.
damn i was just about to try, dark are you on windows 7 or xp?
ManelScout4Life said:
damn i was just about to try, dark are you on windows 7 or xp?
Click to expand...
Click to collapse
I ran it on windows 7. I'm going to try it on xp now and will post the results.
UPDATE: Crashes on xp too.
Thanks for the test, Dark9781.
When you say it's crashing before 4%, what does that mean exactly ? Does is start to flash anything on your phone ? Are the 1st percents only decidacted to do checks on the file ? Do you have a log file ?
Did you try to download the rom a second time to be sure it was not a bad download ? I'm downloading it myself to check if my upload was good (I remember the 1st Incite tests were failing because of errors on upload, that's why the following tests were 7z, I'll do that on the next tests).
Also did you try to extract the stock v10d with dzdecrypt and pack it with dzcreate using another version name (-vTEST_ROM) (just to be sure it's not due to the name and/or the tools).
Sorry for all these questions but it's just to narrow the search.
spocky12 said:
Thanks for the test, Dark9781.
When you say it's crashing before 4%, what does that mean exactly ? Does is start to flash anything on your phone ? Are the 1st percents only decidacted to do checks on the file ? Do you have a log file ?
Did you try to download the rom a second time to be sure it was not a bad download ? I'm downloading it myself to check if my upload was good (I remember the 1st Incite tests were failing because of errors on upload, that's why the following tests were 7z, I'll do that on the next tests).
Also did you try to extract the stock v10d with dzdecrypt and pack it with dzcreate using another version name (-vTEST_ROM) (just to be sure it's not due to the name and/or the tools).
Sorry for all these questions but it's just to narrow the search.
Click to expand...
Click to collapse
Well, the first 4% is just a check of the rom and it is failing causing the flasher program to crash. I'm going to try and download it again to see if it was the download. I didn't try dzdecrypt to take the stock rom apart and dzcreate to put it back together, but I'll try that too.
I used dzdecrypt and dzcreate to deconstruct and reconstruct the stock rom and it flashed fine. I downloaded the test rom again and again the flasher crashes. The message I get is 3GQCT_SP_STARTER MFC (a bunch of weird symbols) stopped working. The log I posted on the last post was the wrong log. It was for another install that failed on me so please ignore that. The flasher didn't create a log for the flasher crashing.
Ok, after a check, it seems that there was a problem during upload (i've found a string "n: close cache-control" in the middle of the uploaded dz file that was not on my version).
I'm reuploading it right now, let's hope it will be fine this time.
Hoping that that was the only problem. I remember that there was a problem with uploads with the Incite. I've been having some problems with uploads lately. Seems to be happening a lot with mediafire. I'll try it again once it is uploaded.
Upload finished, link in 1st post. I've embedded a md5 in the archive.
2Am here, see you in 8h from now
We have a winner. It worked.
UPDATE: The rom flashed, but there are a bunch of things that aren't functioning properly. At least we know that a rom can be put together now.
Dark9781 said:
We have a winner. It worked.
UPDATE: The rom flashed, but there are a bunch of things that aren't functioning properly. At least we know that a rom can be put together now.
Click to expand...
Click to collapse
EXCELLENT!
GREAT WORK GUYS!
well now i'm anxiously awaiting your step by step and what all is needed. cuz i'm ready to get down and dirty with this..
Dark9781 said:
We have a winner. It worked.
UPDATE: The rom flashed, but there are a bunch of things that aren't functioning properly. At least we know that a rom can be put together now.
Click to expand...
Click to collapse
So what exactly isn't functioning correctly?
New test rom available.
Flashing your V3 now, having trouble flashing with the LG IQ Flasher so I am using my Octopusbox to flash.
Ok, phone boots up, but the screen is all black, and non of the buttons seem to work or there is a really long delay to get them to work. Start Menu doesn't work.
Just flashed test 3 and can confirm that I am getting the same results as test 2.
Test 4 gives the same results as test 2 & 3.
Related
Hello guys, I have to ask you a question that I can not resolve for months.
I have a HTC TOUCH PRO, and every kernel I try to always have problems.
At first the device works well and is also very fast, but hopelessly after a while it stops. When you first start can last hours and then crash, but already the second hangs after a few seconds.
I've tried almost every kernel, even the "msm-htc-linux-20101204_005141-package.tar" by the comments that seems to be the best for my device, but nothing. I'm desperate and I do not know what to do.
Can you tell me how to solve this?
Waiting for reply.
Thanks to everyone that I will respond.
I'm not sure what your problem actually is. Sounds like the system_server bug... Make a call to voicemail, phone should speed back up.
Also, the newest kernel is 1253. The autobuild service has fallen behind GIT, see this thread to get the most up-to-date GIT commits.
i must only update with this kernel?
master9 said:
i must only update with this kernel?
Click to expand...
Click to collapse
The kernel (zImage) goes hand-in-hand with the modules file.
Still not sure what you mean tho.
The problem is very simply. Any kernel I use the phone freezes.
This kernel (1253) is very very fast, but nothing, however, the phone freezes.
master9 said:
The problem is very simply. Any kernel I use the phone freezes.
This kernel (1253) is very very fast, but nothing, however, the phone freezes.
Click to expand...
Click to collapse
You say it's fast, but the phone freezes...?
Where does it freeze?
XDAndroid is far from 'stable'...
Us Touch Pro owners can't use 1253 due to certain things reported not working with this kernel. 1243 (i believe 124?) works fine.
djdafreund said:
Us Touch Pro owners can't use 1253 due to certain things reported not working with this kernel. 1243 (i believe 124?) works fine.
Click to expand...
Click to collapse
O___o I did not realize that. All RAPH's...? Do we have logs? I need information man!
I'm not sure about all raph's per-say, but in the other normal FRX03 thread (within the past 4 pages i believe, if that) there was a user or two complaining about something not working (i wish i remembered, maybe data) not working, and i told them to revert back because of issues the new kernel(s) had, and he reported back "thanks, that fixed it." So SOMETHING is wrong for sure with Touch Pro's, but don't know for sure if it effect's diamond user's also. Sorry.
Update- Now i remember, it's http://forum.xda-developers.com/showpost.php?p=10590080&postcount=4072, the screen shifting problem. It shift's the screen over to the left by so many pixels, and get's shifted more and more as your using it. It was actually like 14-15 pages back (too much traffic, LOL), but since i use camera a lot, i am using 1214 (last recent one VC did) as i use his camera build, so i can take picture's. I did witness the screen shifting myself in my separate FRX03 build i have (since just use the camera build though solely). But was using 1241 i believe for my non-camera build.
djdafreund said:
I'm not sure about all raph's per-say, but in the other normal FRX03 thread (within the past 4 pages i believe, if that) there was a user or two complaining about something not working (i wish i remembered, maybe data) not working, and i told them to revert back because of issues the new kernel(s) had, and he reported back "thanks, that fixed it." So SOMETHING is wrong for sure with Touch Pro's, but don't know for sure if it effect's diamond user's also. Sorry.
Update- Now i remember, it's http://forum.xda-developers.com/showpost.php?p=10590080&postcount=4072, the screen shifting problem. It shift's the screen over to the left by so many pixels, and get's shifted more and more as your using it. It was actually like 14-15 pages back (too much traffic, LOL), but since i use camera a lot, i am using 1214 (last recent one VC did) as i use his camera build, so i can take picture's. I did witness the screen shifting myself in my separate FRX03 build i have (since just use the camera build though solely). But was using 1241 i believe for my non-camera build.
Click to expand...
Click to collapse
Oh right, that. Screen shifting seems isolated to the RAPH800 and DIAM500. Probably RAPH500 as well, and I'm not sure what the other DIAM is... perhaps there is a DIAM800, not sure. Either way, seems to only be the CDMA devices.
But of course LOL. I personally love my Touch Pro, but WOULD love to upgrade if i had the money. But yeah, the dreaded shift problem til it's fixed. Not a BIG deal for now, since previous kernals will hold us off til that's fixed.
Nothing, i have the same problem
master9 said:
Nothing, i have the same problem
Click to expand...
Click to collapse
You still haven't properly elaborated on your actual problem. Vagueness will get you nowhere, except frustrate people.
I did not understand what you mean. I'm trying everything I was recommended and I can not solve this problem. I try to re-explain.
The problem is very simple: the phone, any kernel I mountains, after a couple of minutes it stops. I can not wait to give other details because the problem is just that.
Everything works (including wireless), the system is fast but is hopelessly blocked.
When you first start working for hours, just minutes after the second start.
master9 said:
I did not understand what you mean. I'm trying everything I was recommended and I can not solve this problem. I try to re-explain.
The problem is very simple: the phone, any kernel I mountains, after a couple of minutes it stops. I can not wait to give other details because the problem is just that.
Everything works (including wireless), the system is fast but is hopelessly blocked.
When you first start working for hours, just minutes after the second start.
Click to expand...
Click to collapse
Seems to be a pretty big language barrier here... "any kernel I mountains"...?
So has Android ever worked for you? What build(s) have you tried?
Sorry, my fault: "any kernel I mount".
Sorry but i can't speak english very well.
I have try a lot of build: kenya, cyanmod, FRG83.R6 ecc..
but the result don't change.
master9 said:
Sorry, my fault: "any kernel I mount".
Sorry but i can't speak english very well.
I have try a lot of build: kenya, cyanmod, FRG83.R6 ecc..
but the result don't change.
Click to expand...
Click to collapse
What about FRX03? I can't really help you with any build but that one - if you're using a different build, you'll need to get help in those threads. Generally if you just throw up a post like this, use FRX03 (or AOSP, whatever) as your base to test off of.
If it works in that build, but doesn't work in one of the others - then it's that build. If they fail in both builds, then it's a general issue with Android - or, you've just done something wrong .
I also think the same thing because no version I work, all give the same problem.
This is my steps:
1 - Extract all the package (eg superfroyo) to the root of SD, also replace the kernel (of course renaming the new kernel in "zKernel") and also the module, copying them always in the root.
2 - Put the file "startup.exe" HARETSTARTUP of the root and put the file "startup.exe" contained in INSTALL-NPKINSTALL in startups.
3 - Starting in the INSTALL file inside the folder NPKINSTALL.
4 - After the procedure I restart the phone and after i start the file "HARET".
At this point the system starts, it's fast and it all works perfectly but crashes for no reason without giving me the opportunity to do anything, I can only do a soft reset.
Kindly tell me if something wrong in the procedure.
Keep in mind, most neopeek variants require two partiations to be setup as primary (one FAT32 and one EXT2). You might find it a tad difficult in finding someone to help you troubleshoot your process unless you seek help from with-in the thread that you downloaded superfroyo or any other neopeek variants. It is rare to find but then again, you could just as easy try out FRX04 and post your feedback in that thread too. See THIS post for info on downloading the FRX04 update file but you will probably need to downoad THIS package first, then update the system.ext2, rootfs and kernel package after the fact. Stinebd has links for the rootfs in his sig.
n-Joie! (Enjoy)
master9 said:
I also think the same thing because no version I work, all give the same problem.
This is my steps:
1 - Extract all the package (eg superfroyo) to the root of SD, also replace the kernel (of course renaming the new kernel in "zKernel") and also the module, copying them always in the root.
2 - Put the file "startup.exe" HARETSTARTUP of the root and put the file "startup.exe" contained in INSTALL-NPKINSTALL in startups.
3 - Starting in the INSTALL file inside the folder NPKINSTALL.
4 - After the procedure I restart the phone and after i start the file "HARET".
At this point the system starts, it's fast and it all works perfectly but crashes for no reason without giving me the opportunity to do anything, I can only do a soft reset.
Kindly tell me if something wrong in the procedure.
Click to expand...
Click to collapse
Again, you're using funky version. As R^72 said, get help with those versions in that thread.
If you want help, at least try FRX03. You haven't even given it a shot. Then you can update to FRX04, and if that all works - then try something more complicated like a Neopeek build!
Just to reiterate, THIS DOES NOT WORK YET. This thread was created for interested devs who may want the appropriate files to get this going. As far as I know, this doesn't work on anything but the Korean Galaxy.
Ok, so recently the Korean variant of the Galaxy S got a Gingerbread update. (the SHW-M110S)
This phone HAS call recording, and is the best chance of getting call recording to work on Gingerbread.
However, just copying the appropriate files isn't enough. libaudiopolicy.so (the only file needed for recording, as the other 2 broke Fring in the Froyo version) puts the phone into a hard bootloop (doesn't get to boot animation). Phone.apk will force close.
That said, I'm on Darky's 10RC6, which I have previously got into a hard bootloop through a new framework-res.apk suitable for JVB (which it's based on). I encourage you to backup your files and copy these files yourself - if you're lucky, it might work!
I found it a chore to download the entire update tar, mount factoryfs.rfs and extract and deodex the apk and .so files myself, so I'm putting them here to hopefully attract interest in getting this to work.
Attached files are:
/system/app/Phone.apk
/system/app/Phone_util.apk
/system/lib/libaudiopolicy.so
/system/lib/libaudioflinger.so
/system/lib/libaudio.so
/system/framework/twframework-res.apk (required to decompile Phone.apk!!)
/system/framework/framework-res.apk (Also required to decompile Phone.apk!)
Phone.apk is deodexed (framework apks have no need to be), and because I have the ROM downloaded and mountable, I can attach any other files from the ROM that devs may need.
Phone_util.apk is completely unchanged from JVB, so I doubt it is needed for a successful port.
Good luck to all on getting this to work!
For those interested, the tar is:
SHW-M110S_Gingerbread_REV03_ALL_VD27-0629_CL164221_mid_user.tar
Google it if you want to dl yourself a copy.
P.S. Mods - I posted this in dev and not general because I extracted and deodexed the files myself, and there may be more dev exposure here - hoping this is alright. Move if appropriate.
Hope the devs here get this working
Oh, and if it works on CM7, that would be SO hot.
Thanks dude, Can you upload these files also ?
systemp\app\phone_util.apk
systemp\lib\libaudio.so
systemp\lib\libaudioflinger.so
Edit: SHW-M110S_Gingerbread_REV03_ALL_VD27-0629_CL164221_mid_user.tar was already on torrent, I had downloaded it. But I didn't know whether it has call recording or not. Are you sure about that?
sinancetinkaya said:
Thanks dude, Can you upload these files also ?
systemp\app\phone_util.apk
systemp\lib\libaudio.so
systemp\lib\libaudioflinger.so
Click to expand...
Click to collapse
Updated the original post with the files.
And I'm sure it has call recording. The Phone.apk has all the required xmls and images for recording, looking quite similar to the Froyo call recording Phone.apk.
i will test it i ve been waiting for this for a long time
I have package M110S-Gingerbread-HOME-IMAGE-REV03-VE03-0050-USER.tar.md5.
I don't know if it is right version, but it doesn't seem to help.
So far I tried just copying libaudiopolicy.so and Phone.apk, but it didn't work - actually after copying Phone.apk, it started to crash.
Files from this thread didn't work either (same crashing).
K4P1 said:
I have package M110S-Gingerbread-HOME-IMAGE-REV03-VE03-0050-USER.tar.md5.
I don't know if it is right version, but it doesn't seem to help.
So far I tried just copying libaudiopolicy.so and Phone.apk, but it didn't work - actually after copying Phone.apk, it started to crash.
Files from this thread didn't work either (same crashing).
Click to expand...
Click to collapse
Yeah, doesn't seem like it works on any non Korean Gingerbread roms at the moment then. Pity it's not just a darky thing.
montymintypie said:
Yeah, doesn't seem like it works on any non Korean Gingerbread roms at the moment then. Pity it's not just a darky thing.
Click to expand...
Click to collapse
Yep, they should do call recording available to all areas.
Here is some info about this ROM
http://www.phoneinside.co.kr/bbs/board.php?bo_table=about04&wr_id=814
K4P1 said:
I have package M110S-Gingerbread-HOME-IMAGE-REV03-VE03-0050-USER.tar.md5.
I don't know if it is right version, but it doesn't seem to help.
So far I tried just copying libaudiopolicy.so and Phone.apk, but it didn't work - actually after copying Phone.apk, it started to crash.
Files from this thread didn't work either (same crashing).
Click to expand...
Click to collapse
Edit: didn't work
sinancetinkaya said:
Can you try these files via cwm ?
Click to expand...
Click to collapse
Flashing first... Waiting if it boots.
Neither doesn't work. Phone doesn't even get to boot animation stage.
Ok, not working.
I can try other if needed (I just reflash rom again - it takes just a few minutes).
sinancetinkaya said:
Can you try these files via cwm ?
Click to expand...
Click to collapse
For me (Darky's 10RC6 which is based on JVB) both update files give me a hard bootloop (doesn't get past Galaxy S screen).
I noticed you changed the libaudio.so between the 2, what did you do to it?
K4P1 said:
Flashing first... Waiting if it boots.
Neither doesn't work. Phone doesn't even get to boot animation stage.
Ok, not working.
I can try other if needed (I just reflash rom again - it takes just a few minutes).
Click to expand...
Click to collapse
edit: didn't work
montymintypie said:
For me (Darky's 10RC6 which is based on JVB) both update files give me a hard bootloop (doesn't get past Galaxy S screen).
I noticed you changed the libaudio.so between the 2, what did you do to it?
Click to expand...
Click to collapse
It's the original file of froyo. The ginger one you provided is too small. I thought that can't be that much small.
sinancetinkaya said:
Last test, try these please
Click to expand...
Click to collapse
Nope, still boot loops before it gets to the boot animation. The file that's killing it is libaudiopolicy.so, replace nothing but that and it'll bootloop.
How do you decompile a .so file? A google search returns limited information on the topic.
I tried to flash with CWM2 (flashed speedmod k13E), I have changed the files in the update zip of http://forum.xda-developers.com/showthread.php?t=967297 and I used the restore update too... easier way to check it.
The results are that: The phone is even not booting, it's stuck on the I9000 screen and not going to the ROM boot...
I flashed back to original files... wait for good update zip.
orenzah said:
I tried to flash with CWM2 (flashed speedmod k13E), I have changed the files in the update zip of http://forum.xda-developers.com/showthread.php?t=967297 and I used the restore update too... easier way to check it.
The results are that: The phone is even not booting, it's stuck on the I9000 screen and not going to the ROM boot...
I flashed back to original files... wait for good update zip.
Click to expand...
Click to collapse
Same here,I tried with files in this thread and files from "M110S-Gingerbread-HOME-IMAGE-REV03-VE03-0050-USER" rom.
I'm going to flash just the 'lib' '.so' files and check the response of the device, if the device will response right... I'll go further and I'll change the apk's files of the phone, I'll merge the apk's of the i9000 GB with korean GB.
I hope it will be easy as it sound.
orenzah said:
I'm going to flash just the 'lib' '.so' files and check the response of the device, if the device will response right... I'll go further and I'll change the apk's files of the phone, I'll merge the apk's of the i9000 GB with korean GB.
I hope it will be easy as it sound.
Click to expand...
Click to collapse
waiting for a result
zenosteam said:
waiting for a result
Click to expand...
Click to collapse
ok, I flashed.
sadly the phone won't boot, I restored with the backup files, and than it's booted.
The 'lib' '.so' files having problems. I don't know which one of them.
That's means we need here a good developers for working on this.
I can't help anymore of that (I think), I'm just electronic guy not programmer.
orenzah said:
ok, I flashed.
sadly the phone won't boot, I restored with the backup files, and than it's booted.
The 'lib' '.so' files having problems. I don't know which one of them.
That's means we need here a good developers for working on this.
I can't help anymore of that (I think), I'm just electronic guy not programmer.
Click to expand...
Click to collapse
At least it is in libaudiopolicy.so, because try flashing it only and phone won't boot.
First of all I am not a established developer still learning android system...... if anything creates problems after flashing this rom or after installing, dont blame me..
Proudly present the rom for Idol 3 6045I ported from it Chinese sibling TCL I806.
Fully working on my 6045I. Its stock 5.0.2 from TCL I806.
Many chinese apps have been removed but still few remains which can be removed by getting root.
Features:
1. Less Lags.
2. Fast.
3. Camera is working far better than the recent updates provided for 6045I.
How to install:
Caution : Before doing this, please make backup of your system & efs as mentioned by Famewolf in his thread of making backups.
1. Just download the zip from the link provided below and keep it in the root of sdcard.
2. Also download the gapps provided in the links. First link is which I installed on my device and second one is the latest. Keep it also in the root of the sdcard.
3. Now just boot into recovery mode i.e. TWRP , do not wipe anything, script will do it itself and just go to install and choose the stock chinese rom for 6045I.zip and flash.
4. Let the process to complete. It will ask to restart the system and just restart the system.
5. After first start choose language and other options, again boot into recovery mode and flash the gapps provided.
6. Here the stock chinese rom will run smoothly on your 6045I.
7. If TWRP gives error "error in executing binary" then you have to manually edit the updater-script but it depends on what your TWRP says about the error. So just ask me I will tell you what changes to make in updater-script.
After couple of manual restarts or with time rom will start to run smoothly.
Links :
Rom : removed due to some problems occurred after flashing.
gapps : https://www.androidfilehost.com/?fid=95784891001614559 or https://basketbuild.com/gapps (choose android 5.0).
For any kind of help regarding to this rom pm me or just ask in this thread.
I will try my best
Caution : Does not works on 6045Y & 6045K.
Backup efs also in case u loose ur IMEI or having error of unknown baseband/ no network
If you like my work, dont forget to hit thanks......
Sorry for all the trouble caused.
Well I am also in the same boat as well.....
yash_rathore25 said:
First of all I am not a established developer still learning android system...... if anything creates problems after flashing this rom or after installing, dont blame me..
Proudly present the rom for Idol 3 6045I ported from it Chinese sibling TCL I806.
Fully working on my 6045I. Its stock 5.0.2 from TCL I806.
Many chinese apps have been removed but still few remains which can be removed by getting root.
Features:
1. Less Lags.
2. Fast.
3. Camera is working far better than the recent updates provided for 6045I.
How to install:
Caution : Before doing this, please make backup of your system as mentioned by Famewolf in his thread of making backups.
1. Just download the zip from the link provided below and keep it in the root of sdcard.
2. Also download the gapps provided in the links. First link is which I installed on my device and second one is the latest. Keep it also in the root of the sdcard.
3. Now just boot into recovery mode i.e. TWRP , do not wipe anything, script will do it itself and just go to install and choose the stock chinese rom for 6045I.zip and flash.
4. Let the process to complete. It will ask to restart the system and just restart the system.
5. After first start choose language and other options, again boot into recovery mode and flash the gapps provided.
6. Here the stock chinese rom will run smoothly on your 6045I.
7. If TWRP gives error "error in executing binary" then you have to manually edit the updater-script but it depends on what your TWRP says about the error. So just ask me I will tell you what changes to make in updater-script.
After couple of manual restarts or with time rom will start to run smoothly.
Links :
Rom : https://mega.nz/#!88t2jJjT!dFpCY6987LAyAO2CcuKr0wmi5EPB3kRu9v8YTrNBgHs
gapps : https://www.androidfilehost.com/?fid=95784891001614559 or https://basketbuild.com/gapps (choose android 5.0).
For any kind of help regarding to this rom pm me or just ask in this thread.
I will try my best
May also work on 6045Y and 6045K : just need some willing hands.
If you like my work, dont forget to hit thanks......
Click to expand...
Click to collapse
Woohoo. Gonna download this!!!
For screenshots of rom visit this page : http://forum.xda-developers.com/idol-3/development/idol-3-source-code-available-t3180369/page14
Now going to sleep, as have to go office in morning......
Quick question. Can this rom read/write ExFat? I'd rather have my sd card formatted to that so that i can store larger movie files.
Are there any real noticeable differences besides less lag and fast? Those two mean almost the same thing. Does this ROM offer anything major that the US stock ROM doesn't? Awesome work though making a new ROM for the community to try. We appreciate your work. :good:
brian117 said:
Are there any real noticeable differences besides less lag and fast? Those two mean almost the same thing. Does this ROM offer anything major that the US stock ROM doesn't? Awesome work though making a new ROM for the community to try. We appreciate your work. :good:
Click to expand...
Click to collapse
One enhancement I read about was that it did have newer camera software. Many of the packages included are newer version levels than the ones included on our phones because the i806 came out after our models.
---------- Post added at 08:58 PM ---------- Previous post was at 08:45 PM ----------
yash_rathore25 said:
For screenshots of rom visit this page : http://forum.xda-developers.com/idol-3/development/idol-3-source-code-available-t3180369/page14
Now going to sleep, as have to go office in morning......
Click to expand...
Click to collapse
You should consider removing the system update checker from your custom rom. The icon appears in your screenshots so I'm assuming it's still included. Since the build.prop says it's a 6045i but it has the i806 codebase patches will never apply since the checksum's won't match.....so depending on what "version" it thinks it's on vs the update version the update checker will either never show an update or always show an update.
OK. I think I have this working. The ROM seems to be functional for me. Downloading all my apps now and getting it set up how I like. Will try to run it through the day tomorrow and see what I like and don't like... not expecting much difference over stock, but we'll see.
Anyone have a suggestion for a lollipop compatible "minimal gapps?" I'm really only interested in google play and gmail..no need for google+ etc.
famewolf said:
Anyone have a suggestion for a lollipop compatible "minimal gapps?" I'm really only interested in google play and gmail..no need for google+ etc.
Click to expand...
Click to collapse
I might still have a PA micro gapps file somewhere. Just need to see if it's 5.0 or 5.1.
Edit: Here you go. Just pick up the zero gapps. It works perfectly.
http://forum.xda-developers.com/showthread.php?t=2792842
Another option is the Slimgapps official thread here. They do have a "zero gapps" package, and both 5.x I think.
Sent from my 6045Y using XDA Free mobile app
yash_rathore25 said:
May also work on 6045Y and 6045K : just need some willing hands.
Click to expand...
Click to collapse
You mean testers?
Sent from my 6045Y using XDA Free mobile app
Anghirrim said:
You mean testers?
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
Yupp bro.
Just edit build.prop with notepad++ and change it to 6045Y instead of 6045I and flash the rom.
Then check the log of TWRP specially before the error in executing updater binary.
It will say something about the check_cu.
If you will open updater script with notepad++ you will see first line of command saying "check_cu("6045I-2AALUS7");"
Just change this line ("6045I-2AALUS7") with the line shown in the TWRP similar to this ( something like 6045Y-XXXXXXX)
Then again flash the rom, gapps and hope it will work.
If it works, dont forget to hit thanks button :laugh:
Ok... I'll see, my phone is less than one week old and I swore myself that this one would be kept untouched for a year. I wanted to keep it clean for warranty purpose but one week later... I'm already rooted.
I'm kind of flashaholic so won't resist very long... Don't worry.
What will it update exactly? Is there a risk it will mess up the European radio part? Just to make sure I'll still get a good signal or loose imei.
I do have my twrp backup for boot and system image, will that be enough to get back to a previous working state?
Thanks,
Sent from my 6045Y using XDA Free mobile app
Anghirrim said:
Ok... I'll see, my phone is less than one week old and I swore myself that this one would be kept untouched for a year. I wanted to keep it clean for warranty purpose but one week later... I'm already rooted.
I'm kind of flashaholic so won't resist very long... Don't worry.
What will it update exactly? Is there a risk it will mess up the European radio part? Just to make sure I'll still get a good signal or loose imei.
I do have my twrp backup for boot and system image, will that be enough to get back to a previous working state?
Thanks,
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
I rooted my phone the next day it came to me,
Eventually i am also not going to get warranty as I imported this device from US to India.
N I personally dont care about warranty as none of the android device gets bricked completely, there is always a way.
Like I got stucked in bootloops in try of porting cm12.1 from other device.Even my backups failed to boot. Then I followed the mobile updater app provided by Alcatel and it simply restored my device to factory rom which will get updates also.
N warranty will not work if the device got physically damaged.
Yes backup will work.
After flashing this rom I would suggest you to make TWRP backup of this rom also alongwith Stock one.
I am getting a lot of range in network selection as it contains all the radios available for this device.
Screenshots of network range:
Anghirrim said:
Ok... I'll see, my phone is less than one week old and I swore myself that this one would be kept untouched for a year. I wanted to keep it clean for warranty purpose but one week later... I'm already rooted.
I'm kind of flashaholic so won't resist very long... Don't worry.
What will it update exactly? Is there a risk it will mess up the European radio part? Just to make sure I'll still get a good signal or loose imei.
I do have my twrp backup for boot and system image, will that be enough to get back to a previous working state?
Thanks,
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
It's much safer to mod now since with Version 4.9.2 of the Mobile Q software from alcatel (you have to tell it you have a "pixi" for that version to appear as it's so new) allows you to put the phone in "download mode" and fully restore the device to factory condition. (tested by multiple idol 3 users of both the 6039 and 6045) This goes a long way towards making the device unbrickable.
famewolf said:
It's much safer to mod now since with Version 4.9.2 of the Mobile Q software from alcatel (you have to tell it you have a "pixi" for that version to appear as it's so new) allows you to put the phone in "download mode" and fully restore the device to factory condition. (tested by multiple idol 3 users of both the 6039 and 6045) This goes a long way towards making the device unbrickable.
Click to expand...
Click to collapse
I agree with you bro......:good::good:
Thanks both for your answers. Yes the Alcatel restore software makes things way easier to fix. I already installed it yesterday to make sure my phone drivers are installed for any "phone state". I also have the android sdk installed.
By the way, I am thinking to bring my small contribution to this forum by creating an " ultimate list of mods/softwares/issues" for this phone.
There have been so many news and achivements in the past few weeks, it's a bit difficult to read everything in the correct order.
So last question, how about the radio, imei, etc... Any risk on this?
And then, I think I'll give it a try.
Sent from my 6045Y using XDA Free mobile app
Anghirrim said:
Thanks both for your answers. Yes the Alcatel restore software makes things way easier to fix. I already installed it yesterday to make sure my phone drivers are installed for any "phone state". I also have the android sdk installed.
By the way, I am thinking to bring my small contribution to this forum by creating an " ultimate list of mods/softwares/issues" for this phone.
There have been so many news and achivements in the past few weeks, it's a bit difficult to read everything in the correct order.
So last question, how about the radio, imei, etc... Any risk on this?
And then, I think I'll give it a try.
Sent from my 6045Y using XDA Free mobile app
Click to expand...
Click to collapse
In my opinion no risk of losing imei no. and radio modems
yash_rathore25 said:
In my opinion no risk of losing imei no. and radio modems
Click to expand...
Click to collapse
I'm attaching a platform.xml file already modded to allow full read/write access to the external sd (just drop the .zip off the filename as that was just to get xda to allow me to upload it...it's a text file)....you might find it useful to replace this in yours.(/etc/permissions)..other options include pre-rooting...adding in init.d support....etc.
Ran this ROM overnight and through most of my day so far (about 3 hours off the charger). First impression is that it's about the same as stock, not that I was expecting any different. You get the TCL splash screen at boot but the overall UI is pretty much the same. Since I now have root I went ahead and used app quarantine to freeze the bloatware apps I didn't want. Kinda wishing I had installed minimal gapps, but I figure I'll be reflashing again soon since the floodgates are probably about to open with new ROMS anyway.
Conclusion: If you're curious, flash it, it doesn't hurt anything. It may be a hair smoother, and I haven't really tested the camera extensively enough before or after to be able to tell a difference.
Edit: Literally as soon as I submitted this message (from my PC) I went to turn wi-fi off and the phone decided to reboot. Really odd.
@nickalltogether:
Which version of the phone do you have?
Sent from my 6045Y using XDA Free mobile app
Its been a while since I have rooted anything manually and i need some expert advice here.
I have someone unlocking my T399 and he gave me this guide -> http://rootmygalaxy.net/root-galaxy-light-sgh-t399-install-twrp-recovery/ the problem is the TWRP link is dead and i cant find another of that version anywhere. Does anyone have this or can I use http://androidforums.com/threads/recovery-team-win-recovery-twrp-2-7-0-0.836658/ or https://forum.xda-developers.com/ga...recovery-twrp-2-8-1-0-touch-recovery-t2924604 ? Im assuming yes but wanted to double check with you guys before off and doing something catastrophic to my phone.
Any help is much appreciated.
Thanks
Phonecapone
TWRP Themed Recovery
phonecapone said:
Its been a while since I have rooted anything manually and i need some expert advice here.
I have someone unlocking my T399 and he gave me this guide -> http://rootmygalaxy.net/root-galaxy-light-sgh-t399-install-twrp-recovery/ the problem is the TWRP link is dead and i cant find another of that version anywhere. Does anyone have this or can I use http://androidforums.com/threads/recovery-team-win-recovery-twrp-2-7-0-0.836658/ or https://forum.xda-developers.com/ga...recovery-twrp-2-8-1-0-touch-recovery-t2924604 ? Im assuming yes but wanted to double check with you guys before off and doing something catastrophic to my phone.
Any help is much appreciated.
Thanks
Phonecapone
Click to expand...
Click to collapse
There you go
I upload TWRP Themed Recovery on Android file host there you find (IMG,zip,tar) file choose what you want:good:
https://www.androidfilehost.com/?w=files&flid=157735
I used the second one you linked just a couple weeks ago, and it appears to work just fine:
https://forum.xda-developers.com/ga...recovery-twrp-2-8-1-0-touch-recovery-t2924604
A140 said:
There you go
I upload TWRP Themed Recovery on Android file host there you find (IMG,zip,tar) file choose what you want:good:
https://www.androidfilehost.com/?w=files&flid=157735
Click to expand...
Click to collapse
Hey A140 thanks a million! Hopefully I wont have any issues downloading it. For some reason I have had a lot of corrupt downloads from androidfilehost. I know they said they are in the process of moving servers? So perhaps that's why. Can you upload to one more place so we all have a backup here? So in the event others run into the same problem I am having we're all covered. =]
http://www.multiup.eu is good
I will try and download soon as I just got back around to this phone again and give it a try and let you know what I think. Right now I have TWRP ver 2.7.1.0 for Galaxy Light T399 ? which appears to be custom and themed? I just now noticed it when rebooting into Recovery from ROMs restart options. It is white, brown and orange with a list menu. I haven't seen this before though again I haven't flashed any other versions of TWRP besides the touch so maybe it's the standard? I did have TWRP ver 2.8.4.0 for this phone which was the grey, black and blue big button themed touch interface I loved so much.
Aside TWRP matters im also toying around with Lightwave-V3 Rom by user @root@ which I switched to from TigerLillly by user DJBoxer. Both seem to be pretty good although Lightwave was suppose to have came preconfigured with a bunch of useful utilities / mods and it appears they weren't configured in the Rom's configuration. I'll have to take a look and see what needs to be modified if they exist within the build seems same with TigerLilly also. I'd suggest these 2 ROMs to anyone with this phone. Smooth, no bloat and no problems so far. However I am always up for trying any others if anyone has some to suggest. Post and let me know.
First post back here in some months. Now back into androids more and attempting root on a few unknowns so hopefully I will have some good material to contribute in the near future. Still hitting that learning curve hard trying to get with the future. I'm still oldschool @ heart stuck with knowledge of the past flip / feature phones, java, crackberries, outdated unlocking boxes and about 100 pre android phones lol. Have the parts to the first android still but unfortunately incomplete. Some interesting times I tell ya. Thanks to XDA and HOFO I'm picking up where I left off quite quickly.
Lightwave - https://forum.xda-developers.com/galaxy-light/development/rom-lightwave-v1-t2825253
TigerLilly - https://forum.xda-developers.com/galaxy-light/development/rom-tigerlilly-v2-1-4-4-2-t3400659
I will post a TON of information on this phone, recovery, rooting, stock/custom rom links and much more in the appropriate thread when I get time free from work. Have done a lot of researching since this post. https://forum.xda-developers.com/galaxy-light - seems to have most of my work done lol. I keep forgetting how old this phone is and that it's been ran through by quite a few dev's already.
Upload it
I upload both themed 2.7 and 2.8 to your favorite site I am giving the link down you can download from it I upload zip file you can flash using costom recovery that you have right now if you want img file you can extract zip file you find Img file and if you want to flash through odin than use zarchiver on your Android phone and compress img file to tar and rename it tar.md5!?
Themed 2.7 link
http://www.multiup.eu/bd3fdc8bee0f678b90df62a1376ed1e6
TWRP 2.8.4 link
http://www.multiup.eu/en/download/9...14bc32/openrecovery-twrp-2.8.4.0-gardalte.zip
phonecapone said:
Hey A140 thanks a million! Hopefully I wont have any issues downloading it. For some reason I have had a lot of corrupt downloads from androidfilehost. I know they said they are in the process of moving servers? So perhaps that's why. Can you upload to one more place so we all have a backup here? So in the event others run into the same problem I am having we're all covered. =]
http://www.multiup.eu is good
I will try and download soon as I just got back around to this phone again and give it a try and let you know what I think. Right now I have TWRP ver 2.7.1.0 for Galaxy Light T399 ? which appears to be custom and themed? I just now noticed it when rebooting into Recovery from ROMs restart options. It is white, brown and orange with a list menu. I haven't seen this before though again I haven't flashed any other versions of TWRP besides the touch so maybe it's the standard? I did have TWRP ver 2.8.4.0 for this phone which was the grey, black and blue big button themed touch interface I loved so much.
Aside TWRP matters im also toying around with Lightwave-V3 Rom by user @root@ which I switched to from TigerLillly by user DJBoxer. Both seem to be pretty good although Lightwave was suppose to have came preconfigured with a bunch of useful utilities / mods and it appears they weren't configured in the Rom's configuration. I'll have to take a look and see what needs to be modified if they exist within the build seems same with TigerLilly also. I'd suggest these 2 ROMs to anyone with this phone. Smooth, no bloat and no problems so far. However I am always up for trying any others if anyone has some to suggest. Post and let me know.
First post back here in some months. Now back into androids more and attempting root on a few unknowns so hopefully I will have some good material to contribute in the near future. Still hitting that learning curve hard trying to get with the future. I'm still oldschool @ heart stuck with knowledge of the past flip / feature phones, java, crackberries, outdated unlocking boxes and about 100 pre android phones lol. Have the parts to the first android still but unfortunately incomplete. Some interesting times I tell ya. Thanks to XDA and HOFO I'm picking up where I left off quite quickly.
Lightwave - https://forum.xda-developers.com/galaxy-light/development/rom-lightwave-v1-t2825253
TigerLilly - https://forum.xda-developers.com/galaxy-light/development/rom-tigerlilly-v2-1-4-4-2-t3400659
I will post a TON of information on this phone, recovery, rooting, stock/custom rom links and much more in the appropriate thread when I get time free from work. Have done a lot of researching since this post. https://forum.xda-developers.com/galaxy-light - seems to have most of my work done lol. I keep forgetting how old this phone is and that it's been ran through by quite a few dev's already.
Click to expand...
Click to collapse
Thanks again! For conversions and archiving I have been using 7zip and a few simple batch files to convert .tar + calculate sum to .tar.md5 and and .img to .tar then .tar to .tar.md5 calculating sum.
ATTN: I NEED EVERYONE'S HELP!!! PLEASE!!!Here's what I need you to do!Find and Search through your PC's and look for any complete or decently stable ROM's, RECOVERY's, KERNEL's and any possible missing links / files / documents for the LG Optimus V regardless of it's version or kernel and Send me WORKING links, files, of anything you got. All the links for this phone are dead... I've checked all over the web. This is still a great phone, and can still be used either with Boost Mobile or simply with a Credit or Debit card. A friend and I plan on revamping this phone to see if we can't bring it back to it's glory. But in order to do so.... Got to have the Archives! Every link is dead.... PLEASE PLEASE PLEASE search around for anything LG Optimus V, VM670, Thunderc Optimus S is also appreciated.
THANK YOU FOR YOUR TIME AND PATIENCE
Send them to me, in a PM and or share them with me to my Google Drive via email.... PM for email... thanks
You may post links here only as long as the owner hasn't pulled the files for TOS Violations.
To be honest.... if your unsure, just PM the links.
I'm taking any and all files that are DEAD links
anything I can redownload as of today's date, will be unwanted.
But don't let that discourage you from SHARING THEM AWESOME FILES AND RE-UPLOADED LINKS!
THANK YOU THANK YOU THANK YOU!!!
:good::laugh:
I left a reply regarding KitKat and twrp in the hijacked mmarz thread.
as far as active links, here's one:
https://sites.google.com/site/bobzhomeroms/
also be aware when messing with recovery and roms on the Optimus V, you'll be fine if you have the original display (I think that's the Hitachi but may be the Novatek.)
it's been so long I forget which was which.
but during production, lg decided to add a different screen manufacturer, updated their kernel source with a driver to handle both.
older kernels than that will only drive the original screen.
I made a big stink about it for a while, while there was still development going on, and eventually people started patching their kernel configs to turn on the newer screens too, once everyone realized I knew what I was talking about.
so if you have the original screen model, you're golden. if you have a new screen and flash an older rom or recovery (like xionia, for example) you'll get a black screen with backlight instead of display output and be left with nothing but adb or poking around at the display blind.
fair warning.
Here's some Optimus S stuff I used to use,was able to download from here today, https://archive.midnightchannel.net/zefie/files/cell/LGLS670/
bigsupersquid said:
I left a reply regarding KitKat and twrp in the hijacked mmarz thread.
as far as active links, here's one:
https://sites.google.com/site/bobzhomeroms/
also be aware when messing with recovery and roms on the Optimus V, you'll be fine if you have the original display (I think that's the Hitachi but may be the Novatek.)
it's been so long I forget which was which.
but during production, lg decided to add a different screen manufacturer, updated their kernel source with a driver to handle both.
older kernels than that will only drive the original screen.
I made a big stink about it for a while, while there was still development going on, and eventually people started patching their kernel configs to turn on the newer screens too, once everyone realized I knew what I was talking about.
so if you have the original screen model, you're golden. if you have a new screen and flash an older rom or recovery (like xionia, for example) you'll get a black screen with backlight instead of display output and be left with nothing but adb or poking around at the display blind.
fair warning.
Click to expand...
Click to collapse
So the JB rom boots okay,how do i setup Sprint apn/keylayout?
bigsupersquid said:
I left a reply regarding KitKat and twrp in the hijacked mmarz thread.
as far as active links, here's one:
https://sites.google.com/site/bobzhomeroms/
also be aware when messing with recovery and roms on the Optimus V, you'll be fine if you have the original display (I think that's the Hitachi but may be the Novatek.)
it's been so long I forget which was which.
but during production, lg decided to add a different screen manufacturer, updated their kernel source with a driver to handle both.
older kernels than that will only drive the original screen.
I made a big stink about it for a while, while there was still development going on, and eventually people started patching their kernel configs to turn on the newer screens too, once everyone realized I knew what I was talking about.
so if you have the original screen model, you're golden. if you have a new screen and flash an older rom or recovery (like xionia, for example) you'll get a black screen with backlight instead of display output and be left with nothing but adb or poking around at the display blind.
fair warning.
Click to expand...
Click to collapse
I remember from back in the day we had the screen problem... You fixed and addressed it...
But some ROM I baked up didn't work even with the fix... I had the Kernel made with the ROM and the screen still didn't work... I'm working past that now as a matter of fact.
Wasen't it the Pickasticks Recovery... or a file... or something either way I found your old post...
Worked with LesileAnn with somethings too Haha Thank you again for the long lost files!!
timjames474 said:
So the JB rom boots okay,how do i setup Sprint apn/keylayout?
Click to expand...
Click to collapse
I might be able to help you, Tell me what ROM exactly and what it says is WORKING and NOT WORKING on the main page of the post... or a link... It could be like you said a simple set up.
But I do remember having to change something to get other carriers to work. Because it was only a CDMA phone. No GSM. If I remember correctly
redbaron2005 said:
I remember from back in the day we had the screen problem... You fixed and addressed it...
But some ROM I baked up didn't work even with the fix... I had the Kernel made with the ROM and the screen still didn't work... I'm working past that now as a matter of fact.
Wasen't it the Pickasticks Recovery... or a file... or something either way I found your old post...
Worked with LesileAnn with somethings too Haha Thank you again for the long lost files
Click to expand...
Click to collapse
you have to crack open the boot.img and replace just the kernel with a working one. it's "fun."
and finding a working kernel for the newer screens now as a standalone download is really iffy. (actually, see next post. I found /one./)
if you have another jb rom with working screen you can split that boot.img and yoink its kernel for the one that doesn't have more than a backlight. you can also plop that picasticks kernel from below into any blackscreen recovery images too, they split and recombine just like a boot image.
a lot of people call the boot.img a kernel, but it's actually a combination of kernel and ramdisk.
you can use osm0sis AIK tools to disassemble and reassemble boot.img relatively painlessly.
I'm happy to promote osm0sis's work. he does great things. drop him a donation if you're so inclined, he certainly deserves it.
by the way, don't try to insert the 3.0 kitkat kernel into anything else... it probably won't boot. jb is the best bet to try it on though, thekraven nudged me into porting that kernel from the p500 for his jb roms. I'm glad he did, because the experience has been very useful on other devices.
ok, here's my gift to y'all.
https://www.androidfilehost.com/?w=files&flid=317344
archive of the primary goodies from my old failing NTFS external drive. We'll see how long it takes for androidfilehost to arbitrarily delete them like they did every other file I ever uploaded there for the optimus S/V with no warning or acknowledgment. they never even answered multiple support requests trying to find out why... I'm guessing they decided to clean their servers of things uploaded before a certain date, but no telling since they wouldn't answer.
in the kernels subfolder is a picasticks kernel i built for the old/new screens.
multiple recoveries. some are old and may blackscreen on newer devices, fair warning. some roms will be the same way. the twrp's may or may not have reversed system/userdata like my os2sd twrp, try and see. they should at least be good on any model optimus s/v screen.
several roms, including one harmonia, and PAC-rom from thekraven.
others folder has V drivers... and swype flashable zip, ripped probably from GB stock, maybe from froyo stock.
also multirom recoveries and installer if you like multiboot. thread here
have fun.
redbaron2005 said:
I remember from back in the day we had the screen problem... You fixed and addressed it...
But some ROM I baked up didn't work even with the fix... I had the Kernel made with the ROM and the screen still didn't work... I'm working past that now as a matter of fact.
Wasen't it the Pickasticks Recovery... or a file... or something either way I found your old post...
Worked with LesileAnn with somethings too Haha Thank you again for the long lost files!!
I might be able to help you, Tell me what ROM exactly and what it says is WORKING and NOT WORKING on the main page of the post... or a link... It could be like you said a simple set up.
But I do remember having to change something to get other carriers to work. Because it was only a CDMA phone. No GSM. If I remember correctly
Click to expand...
Click to collapse
i got data fine it was more the keys that was bugging the **** outta me
this one here from another link posted here,i use Tello,which uses Sprints MMSC,and yes i figured out actvating data just last week! Downgrade to ZVD and let HFA run. Thats literally it
forgot the link https://sites.google.com/site/bobzhomeroms/vm670jb
timjames474 said:
i got data fine it was more the keys that was bugging the **** outta me
this one here from another link posted here,i use Tello,which uses Sprints MMSC,and yes i figured out actvating data just last week! Downgrade to ZVD and let HFA run. Thats literally it
forgot the link https://sites.google.com/site/bobzhomeroms/vm670jb
Click to expand...
Click to collapse
you need the correct .kl file, I've probably got one stashed somewhere.
it switches the two keys in software.
it's funny, because both the virgin and sprint phones have the same board, but the firmware reverses which key is read as which.
I'll look around and try to find the .kl file for you. androidfilehost deleted my flashable zips with those along with everything else for the S/V a while back as I was complaining about above, or I'd just point you there.
bigsupersquid said:
you need the correct .kl file, I've probably got one stashed somewhere.
it switches the two keys in software.
it's funny, because both the virgin and sprint phones have the same board, but the firmware reverses which key is read as which.
I'll look around and try to find the .kl file for you. androidfilehost deleted my flashable zips with those along with everything else for the S/V a while back as I was complaining about above, or I'd just point you there.
Click to expand...
Click to collapse
if you manage to find it,do let me know! TIA
timjames474 said:
if you manage to find it,do let me know! TIA
Click to expand...
Click to collapse
I can pull the one from the rom on my V and switch the keys.
no flashable zip, you'll have to use adb to install it, I'll post the commands
it's home and menu that are swapped if I remember right, is that correct?
it's actually a .kcm file, I've messed with so many devices I mix things up sometimes.
Sorry for being gone so long,yes those are the keys,my Optimus S had been dropped one time too many but i finally replaced it and am still interested in getting those files and commands
alright, I'll pull the file and swap those two keys.
I don't remember any oddball locations for the file across different roms... but since it has been a while since I did anything much with this device, just to make sure, I'll add a test to the instructions to make sure it's going into the right location.
bigsupersquid said:
alright, I'll pull the file and swap those two keys.
I don't remember any oddball locations for the file across different roms... but since it has been a while since I did anything much with this device, just to make sure, I'll add a test to the instructions to make sure it's going into the right location.
Click to expand...
Click to collapse
Seems that it always goes to /system/usr and the two folders are keylayout and key(something else idr) the one that i cannot remember the name for is where the .kcm files are at
since harmonia has two applicable .kl files, thunder.kl and thunder_keypad.kl I'm not sure which to mess with.
they're in /system/usr/keylayout/
the process is to adb pull the thunder*.kl file from your working ROM (whichever file it is, thunder.kl or thunder_keypad.kl,) back it up on computer with a copy in case you mess it up, then:
change all instances of HOME to MENU and MENU to HOME. I can't remember how much difference the WAKE and WAKE_DROPPED field makes, but you can switch those too, or leave that alone and try it.
if you're using M$ window$, don't push the enter/return key while editing unless you're editing with notepad++, the default editor screws up carriage return line feed character codes. mac or linux shouldn't dork up the CRLFs.
chmod 644 the file after pushing it back, and chown root:root
I'd have to grab it from one of the cm rom files I uploaded for a better reference, and I'd rather not re-download them or try to get my failing external drive they're on to mount at the moment.
bigsupersquid said:
since harmonia has two applicable .kl files, thunder.kl and thunder_keypad.kl I'm not sure which to mess with.
they're in /system/usr/keylayout/
the process is to adb pull the thunder*.kl file from your working ROM (whichever file it is, thunder.kl or thunder_keypad.kl,) back it up on computer with a copy in case you mess it up, then:
change all instances of HOME to MENU and MENU to HOME. I can't remember how much difference the WAKE and WAKE_DROPPED field makes, but you can switch those too, or leave that alone and try it.
if you're using M$ window$, don't push the enter/return key while editing unless you're editing with notepad++, the default editor screws up carriage return line feed character codes. mac or linux shouldn't dork up the CRLFs.
chmod 644 the file after pushing it back, and chown root:root
I'd have to grab it from one of the cm rom files I uploaded for a better reference, and I'd rather not re-download them or try to get my failing external drive they're on to mount at the moment.
Click to expand...
Click to collapse
I was able to pull from CM7 for LS670 and swap,fix perms and voila! Also noticed getting gapps to work on BobzHomes jb is a PITA,as there appears to be no setupwizard so it thinks its in setup,but its not. i looked at build.prop and shut off the setupwizard bypass but nothin. Nearing the point where i say frick gapps at this point
timjames474 said:
I was able to pull from CM7 for LS670 and swap,fix perms and voila! Also noticed getting gapps to work on BobzHomes jb is a PITA,as there appears to be no setupwizard so it thinks its in setup,but its not. i looked at build.prop and shut off the setupwizard bypass but nothin. Nearing the point where i say frick gapps at this point
Click to expand...
Click to collapse
yeah, gapps suck. and it's even worse dealing with them on a device which has such a small system and data partition.
you might look into microg. I prefer it anyway.
glad you got the keyswap to work.
bigsupersquid said:
yeah, gapps suck. and it's even worse dealing with them on a device which has such a small system and data partition.
you might look into microg. I prefer it anyway.
glad you got the keyswap to work.
Click to expand...
Click to collapse
MicroG has a broken login,the login box is all the way off screen for me,but ive since gotten a modern phone at the gentle prodding at Tello anyway