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!
Related
Hello, I have an AT&T Tilt 2 and when I want to boot off xdandroid 2.2.1 I did the .cab file, soft reset, startup.txt, went into the program, update, boot. It types a bunch of codes, and stops at misc_register(): OK. And it stays there as long as I can see! It won't go any further, however, when I restart the phone, it boots normally in to WinMo. I'm running the stock shipped ROM. Does that have anything to do with it? I'm not getting any errors or anything, just stuck at that. And I know it's not me not waiting, because I've sat it down for 2 hours straight! Please help I really want Android on my Tilt 2.
P.S. I've tried RAR and CAB, also the Reference & Froyo!
Try a clean bundle. Format the card using the HP tool. Full format, FAT32.
Also, try this bundle. It's the newest of the new.
thephoneguru said:
Hello, I have an AT&T Tilt 2 and when I want to boot off xdandroid 2.2.1 I did the .cab file, soft reset, startup.txt, went into the program, update, boot. It types a bunch of codes, and stops at misc_register(): OK. And it stays there as long as I can see! It won't go any further, however, when I restart the phone, it boots normally in to WinMo. I'm running the stock shipped ROM. Does that have anything to do with it? I'm not getting any errors or anything, just stuck at that. And I know it's not me not waiting, because I've sat it down for 2 hours straight! Please help I really want Android on my Tilt 2.
P.S. I've tried RAR and CAB, also the Reference & Froyo!
Click to expand...
Click to collapse
Greetings,
I too have a Tilt 2. In the past I've had many problems with xdandroid and other android ports. I personally prefer to use the manual installation, that way I can control what and where things are placed. I'm currently running the the latest FRX04 release on my Tilt2. Here is how I got it working.
1..Download the RAR package.
2..Format your SD Card (not a quick format)
3..Copy the andboot directory to your SD Card
4..Replace the startup.txt with the one attached here.
5..In WinMo run Haret and let it do it's thing.
6..Once in Android test all your apps.
This worked for me, but until I switched to a newer SD Card I would have random reboots and hang ups.
Post any more complications you have I may be able to help you.
dcmedic said:
Greetings,
I too have a Tilt 2. In the past I've had many problems with xdandroid and other android ports. I personally prefer to use the manual installation, that way I can control what and where things are placed. I'm currently running the the latest FRX04 release on my Tilt2. Here is how I got it working.
1..Download the RAR package.
2..Format your SD Card (not a quick format)
3..Copy the andboot directory to your SD Card
4..Replace the startup.txt with the one attached here.
5..In WinMo run Haret and let it do it's thing.
6..Once in Android test all your apps.
This worked for me, but until I switched to a newer SD Card I would have random reboots and hang ups.
Post any more complications you have I may be able to help you.
Click to expand...
Click to collapse
ooooooh!
I will try this startup for my tilt2!
I am having issues like screen landscaping wrong way sometimes etc.
I will report back. Perhaps we get them to pack your startup in the file under "Tilt 2 ATT GSM" or something!
What SD card did you end up getting?
Thanks!
Prodeje79 said:
ooooooh!
I will try this startup for my tilt2!
I am having issues like screen landscaping wrong way sometimes etc.
I will report back. Perhaps we get them to pack your startup in the file under "Tilt 2 ATT GSM" or something!
What SD card did you end up getting?
Thanks!
Click to expand...
Click to collapse
I already had multiple sd cards, Tiad brought it up to try and change my sd card in a conversation the other day, but I'm using a SanDisk 2GB. My SanDisk 4GB is about 4 years old and believe they do wear out. Older cards aren't good for what we need here, since they are basically or on board device storage.
As for the landscaping, sometimes if a hold the phone flat it will switch to landscape left or right, but I usually do not have a problem when I'm holding it in the orientation I'm needing.
That is the same startup file I have used through out 3 different builds. FRX03, FRX04, and FROYO X. I did have overclocking in there, but come to find out it didn't help, I feel that it probably was the cause of a few of my restarts.
I hope everything works out for you. Report back..
dcmedic said:
I already had multiple sd cards, Tiad brought it up to try and change my sd card in a conversation the other day, but I'm using a SanDisk 2GB. My SanDisk 4GB is about 4 years old and believe they do wear out. Older cards aren't good for what we need here, since they are basically or on board device storage.
As for the landscaping, sometimes if a hold the phone flat it will switch to landscape left or right, but I usually do not have a problem when I'm holding it in the orientation I'm needing.
That is the same startup file I have used through out 3 different builds. FRX03, FRX04, and FROYO X. I did have overclocking in there, but come to find out it didn't help, I feel that it probably was the cause of a few of my restarts.
I hope everything works out for you. Report back..
Click to expand...
Click to collapse
will do!
which exact package are you using now?
link appreciated if not already posted above.
Is it a good idea to delete the ts-calibration file as in XDAndroid2.2Froyo.012211 ?
Any other cleanup measures?
Prodeje79 said:
will do!
which exact package are you using now?
link appreciated if not already posted above.
Is it a good idea to delete the ts-calibration file as in XDAndroid2.2Froyo.012211 ?
Any other cleanup measures?
Click to expand...
Click to collapse
I'm using the same package as arrrrrgh posted in Post #2. I just left the touch screen calibration file that came with the package. No other clean up, other than full format to fat32 with your preferred utility.
dcmedic said:
I'm using the same package as arrrrrgh posted in Post #2. I just left the touch screen calibration file that came with the package. No other clean up, other than full format to fat32 with your preferred utility.
Click to expand...
Click to collapse
OK cool, I will give that load a shot tonight.
As of now I am using: XDANDROID.2.2.1.AOSP.FRX03.21.11.10.FULL_PACKAGE
My screen issues are gone now with those tweaks! thanks so much!!!
Although now this thing seems dog slow.
I took out my line "clock-7x00.a11=500" which I think is just stock anyway.
You do not use this command as you noted issues overclocking. Thus yours should be stock speed too right?
This thing is sloooooow now from earlier with my old 'incorrect' stock config in the RAR package.
I also have the weird typing issue in which I press c once (on the hard keyboard slideout), but cccc appears. I think if I type a word super slow, it works better.
So if i type cingular at a decent pace, it will type out 'ccccingularrr'
Any leads on that?
you may need to delete your data.img file and rebuild it with the new startup.txt. that way android is running at stock speed during the setup. shot in the dark.
Sent from my Tilt 2 using the XDA mobile application powered by Tapatalk
Prodeje79 said:
OK cool, I will give that load a shot tonight.
As of now I am using: XDANDROID.2.2.1.AOSP.FRX03.21.11.10.FULL_PACKAGE
My screen issues are gone now with those tweaks! thanks so much!!!
Although now this thing seems dog slow.
I took out my line "clock-7x00.a11=500" which I think is just stock anyway.
You do not use this command as you noted issues overclocking. Thus yours should be stock speed too right?
This thing is sloooooow now from earlier with my old 'incorrect' stock config in the RAR package.
I also have the weird typing issue in which I press c once (on the hard keyboard slideout), but cccc appears. I think if I type a word super slow, it works better.
So if i type cingular at a decent pace, it will type out 'ccccingularrr'
Any leads on that?
Click to expand...
Click to collapse
Holy crap dude... search. You've asked so many questions that have been answered previously, seriously.
With that said, all the issues you describe are all related to the system_server bug. Just make a call to voicemail (or any call really) and it'll clear up. We're looking into the cause and a potential solution.
dcmedic said:
Greetings,
I too have a Tilt 2. In the past I've had many problems with xdandroid and other android ports. I personally prefer to use the manual installation, that way I can control what and where things are placed. I'm currently running the the latest FRX04 release on my Tilt2. Here is how I got it working.
1..Download the RAR package.
2..Format your SD Card (not a quick format)
3..Copy the andboot directory to your SD Card
4..Replace the startup.txt with the one attached here.
5..In WinMo run Haret and let it do it's thing.
6..Once in Android test all your apps.
This worked for me, but until I switched to a newer SD Card I would have random reboots and hang ups.
Post any more complications you have I may be able to help you.
Click to expand...
Click to collapse
Hello, thank you for the quick response. I did exactly what you said. And once I tap Haret it codes and stops at misc_register(): OK still... Any other suggestions? Thank you agian.
it probably doesn't matter, but is your phone all unlocked etc and able to be flashed with any winmo rom?
using olipro?
just trying to think of any differences with our phones.
Prodeje79 said:
it probably doesn't matter, but is your phone all unlocked etc and able to be flashed with any winmo rom?
using olipro?
just trying to think of any differences with our phones.
Click to expand...
Click to collapse
What is unlocked? Isn't that where T-Mobile would be able to use it?? If not, please explain. Sorry for my stupidness. lol
Is it like jailbreaking and/or rooting?
You do not need to do hardSPL unlocking to use Android from the SD card.
I would imagine with NAND builds you would... but since this all runs off the SD card, no need for HSPL.
Assuming you're using that build that was posted in post #2, it should work just fine - did you make any changes to it, or just extract it to the root of your SD and hit haret.exe...?
thephoneguru said:
What is unlocked? Isn't that where T-Mobile would be able to use it?? If not, please explain. Sorry for my stupidness. lol
Is it like jailbreaking and/or rooting?
Click to expand...
Click to collapse
well mainly just the hard SPL unlocking. Not the sim.
very easy.
see the stickies here: http://forum.xda-developers.com/forumdisplay.php?f=490
mainly:
Hard-SPL Unlocker for Rhodium (AT&T Tilt 2) Released and Updated! New FAQ added!
http://forum.xda-developers.com/showthread.php?t=550131
and flashing...
[Resources] Flashing your First GSM Rhodium Rom (For Noobs)
http://forum.xda-developers.com/showthread.php?t=550540
if you do this don't forget to task 29!
http://forum.xda-developers.com/showthread.php?t=649191
I use the energy rom GTX:
http://forum.xda-developers.com/showthread.php?t=562773
I just backed up all my contacts on my SD card with pimbackup and restored them to the new rom....
Again, to thephoneguru - you do not need to do that ^^.
Only if you want to install a custom WinMo ROM, or if you're flashing to full Android (which is not recommended at the moment!) do you need to do HSPL.
arrrghhh said:
You do not need to do hardSPL unlocking to use Android from the SD card.
I would imagine with NAND builds you would... but since this all runs off the SD card, no need for HSPL.
Assuming you're using that build that was posted in post #2, it should work just fine - did you make any changes to it, or just extract it to the root of your SD and hit haret.exe...?
Click to expand...
Click to collapse
I did not make any changes at all I just put the androot directory on the root of my sd, went to the file explorer and tapped haret.exe. Also, the sd card was just formatted (non quick format) to FAT32.
arrrghhh said:
Again, to thephoneguru - you do not need to do that ^^.
Only if you want to install a custom WinMo ROM, or if you're flashing to full Android (which is not recommended at the moment!) do you need to do HSPL.
Click to expand...
Click to collapse
well we get the picture!
its the only difference I can think of in our phones.
I say give it a shot, it is so simple!
Prodeje79 said:
well we get the picture!
its the only difference I can think of in our phones.
I say give it a shot, it is so simple!
Click to expand...
Click to collapse
How is it so simple? Can you explain the procedure? Thank you.
thephoneguru said:
How is it so simple? Can you explain the procedure? Thank you.
Click to expand...
Click to collapse
He posted a lot of links on how to do it... Post #15?
It won't have any effect on your issue tho. It'll only enable you to flash custom ROMs if you so choose to do so.
Let's focus on your issue. Can you tell me where it stops? Does it always stop at the same place? Have you tried different kernels? Any different builds? Have you tried the newest FRX04 build?
ROOTSide ROM
Base Flipside ROM with root/busybox/unknown sources enabled. Only thing different in this rom than rooting it yourself is you get to check/uncheck unknown sources. Yes, that means you can turn unknown sources ON and OFF! I have a clockworkmod recovery folder zipped up for distribution, but I want to post a full-fledged ROM zip file for the masses. PM me, and I will send you the ZIP file that I have right now.
What you get:
base install for the flipside (AT&T) with motoblur ready to set up. It is the exact same thing as doing a factory reset, but you get all the benefits of superuser with busybox and the addead feature of having unknown sources checkbox in the settings.
I will work towards a deoxed version this weekend as well.
No custom bootscreen (yet). No custom anything, really.
Almost There
I am currently in the middle of Deodexing the image. I have added in wifi tethering, and ensured it will have superuser and busybox pre-packaged. Next step is pushing this to my wife's phone and not having her get a pretty brick in return. If all goes well, I will be posting the image by morning light (CST).
Fingers Crossed!
Well
Things didn't go too well with my first build attempt. Appears to be a permission issue with the /system folder. I will sleep on it, and give it a second go in the morning. Sorry for the apparent "tease". If you want a faster build, I could use some other devs working with me.
Hey man, sounds like you're doing great! Keep it up...I already found a way to get the root with unknown sources checked, so i'm just gonna wait for the deoxed version! Hope it goes well as you try again.
Current Issues
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Me too...good luck!!
jonsjava said:
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Click to expand...
Click to collapse
Both of those files are att/moto bloat... just be rid of them
Sent from my MB508 using XDA App
Glad to see some work on this device, I love the form factor but it's obviously not very popular with devs...
Very interested to see this come around. I would like to streamline the wife's phone. Her battery life is a 1/3 of my rooted and flashed X10. Sadly though I am NOT a Dev nor even a cook.
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
so I was curious, I was able to get to unlock mode with an sqlite thing and it worked just fine for me, but have you been able to knock out the bloat and stuff? cause it sounds like the makings of a custom rom lol
you know what the turtle said.. slowly but surely I will win this race
jonsjava said:
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
Click to expand...
Click to collapse
Several ppl have said they have run into this problem...don't know what the deal is...
Is it possible to get CM7, or it's a problem with a locked kernel?
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
jonsjava said:
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
Click to expand...
Click to collapse
sounds good man, keep us posted on progress!!
So check this out...I messaged the guy at modmymobile and asked how things were going becuase I heard people were having problems getting an updated CMW and this is his response:
"been sittin on the updated cwm recovery binaries and been draggin my feet/takin a break the past week or 2. i'll throw something out soon, but cant commit to a timeframe, sorry."
Looks like things are on the up and up...stay patient everyone
GOOD JOB!!!,
We are waiting for the rom
Dukenukemx said:
Is it possible to get CM7, or it's a problem with a locked kernel?
Click to expand...
Click to collapse
I can't install CM7, it reboots and locks up, then I have to reinstall froyo. It never worked when I had eclair either.
all the viperx version reboots while receiving calls! but sometimes it wont reboots....
i've changed it with other rom problem solved,but i love viperx more.... anyone know how to fix it?
Which one are you on now, the JB ? And if you are using the aosp lockscreen mod in the venom tweaks....turn it off and use the standard lockscreen. Might solve your issue
Also Make sure you have deleted the OTA update file from downloads folder.
Apparently recovery goes hyper if you dont (according to viperx thread )
A noobs solution
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
webDing said:
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
Click to expand...
Click to collapse
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Mr Hofs said:
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Click to expand...
Click to collapse
Wow, 3.7.0 (my version) is very old...well at least I didn't post a stupid question, just a stupid answer...
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Mr Hofs said:
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Click to expand...
Click to collapse
No, that was no sarcasm, I'm completely new to rooting phones and I thought progress was very quick and that my version had become obsolete very fast, or that I downloaded an old version.
I still have the problem, well not after disabling the setting...
I did a full wipe.
...but I flashed an old version, noticed my mistake, and then flashed 3.7.0.
The problem is that I know I did a full wipe before flashing the old version, but I'm not 100 per cent sure that I did it the second time. It sounds like missed it. So starting all over again would solve my problem? No short cuts?
Sorry about the misunderstanding!
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Mr Hofs said:
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Click to expand...
Click to collapse
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Hmm buggers, i can't really help you on this because i can't reproduce the reboots. Weird ! But at least thanks for testing
webDing said:
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Click to expand...
Click to collapse
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
webDing said:
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
Click to expand...
Click to collapse
I’ve been a Beta tester for a an American software company during a period of 7-8 years and I’ve written some simple plug-ins for their web design software. So, I tried to use that experience to do some testing and trying to minimize the number of factors that could trigger the problem.
What I did was a factory reset, a wipe and then I installed 3.7.0.
Before installing any apps, launchers and whatnot, I tried running the phone with both pin code and Viper screen lock enabled.
The result was the same every time.
I then tried to enabled the two settings in different orders, first pin code, then Viper and vice versa, but to no avail.
My conclusion, whatever it’s worth, is that it’s easy to get a problem when two pieces of code are trying to manage the same event. Maybe it’s possible to find the line/lines in the code that might trigger the conflict..?
…or maybe Viper just don’t like Sweden/Swedes?
Well, with a little (bad) luck maybe some other people run into this problem, but there might be very few of us who use Viper in this type of configuration…
I don’t think I can add anything more than this, so I’ll leave this issue in the competent hands of those who wrote Viper.
Thanks!
I just bought one! and love CM since the release of my first android phone, the Samsung Galaxy S2
There are only custom roms for the 8.4 and the 10.1 version.
There are no custom ROMs available for this device now, and i hate the slurpy/fancy samsung interface.
I am willing to pay for it, for the first nice and clean nightly CM 11 rom + CWM/TWRP recovery and working Gapps for this device.
This device is out for a while now and there are still no custom roms for.
So i hope there is somebody who can help, to get the custom roms madness for this device getting started.
I got you covered.
I can make a stock custom rom which has all the samsung junk removed so the tablet can go faster.
I want a rooted aosp rom, like cyanogenmod or something.
Are you able to do that?
ExoRRSmits said:
I want a rooted aosp rom, like cyanogenmod or something.
Are you able to do that?
Click to expand...
Click to collapse
Unfortunately, I can't. (I have a 10.1 and I want the same thing). The thing is the processor is a exynos 5 or something like that and it is (as I have read and understood) quite hard to do. I've tried to learn about making it but trust me it is much more harder than it seems. Even my 10.1 doesn't have CM yet. Still if you like I can make a you a stock debloated rom so it will at least run faster than what you have now.
ik4evr2 said:
I got you covered.
I can make a stock custom rom which has all the samsung junk removed so the tablet can go faster.
Click to expand...
Click to collapse
I am very much interested in this thanks!
nickster1 said:
I am very much interested in this thanks!
Click to expand...
Click to collapse
No problem at all. It will take me a day or two.
ik4evr2 said:
No problem at all. It will take me a day or two.
Click to expand...
Click to collapse
Can you make deodex please? I already have the stock debloate, but would be nice to have deodexed rom.
ik4evr2 said:
Unfortunately, I can't. (I have a 10.1 and I want the same thing). The thing is the processor is a exynos 5 or something like that and it is (as I have read and understood) quite hard to do. I've tried to learn about making it but trust me it is much more harder than it seems. Even my 10.1 doesn't have CM yet. Still if you like I can make a you a stock debloated rom so it will at least run faster than what you have now.
Click to expand...
Click to collapse
Well for now it sounds ok to me.
Is it rooted as well?
How debloated is it? Is samsung touchwiz removed?
That's what i'm hating the most. The settings app with tabs, i like the whole settings menu in cm.
And how fast can it see the light?
If its very nice, i can donate something for your good and hard work.
There might be a debloated deodexed rom already here?: http://forum.xda-developers.com/showthread.php?t=2776206
Ludespeed said:
There might be a debloated deodexed rom already here?: http://forum.xda-developers.com/showthread.php?t=2776206
Click to expand...
Click to collapse
No, I tried it, and unfortunately it doesn't work for the 12.2 version. The internal, as well as the external sd card both are locked, meaning you can't even update any apps, or saving any data... you get an error message 110, from Play Store.
ik4evr2 said:
No problem at all. It will take me a day or two.
Click to expand...
Click to collapse
Any luck ?
ExoRRSmits said:
Any luck ?
Click to expand...
Click to collapse
+1!
What about an overclock kernel? I debloated my Galaxy tab 12.2 already but have yet to successfully overclock it. I've been looking everywhere for an improved kernel or something to improve the performance, debloating didn't help it that much so a kernel or custom rom would be the next bet. Anyone point me in the right direction?
In school atm, but had a few mins so I built this: https://drive.google.com/file/d/0B5kaDFDMK0TYci14Nm1EOFFnX2s/edit?usp=sharing
Can't reply to any question atm but will when I get home. Not sure if it will boot.
Download, advance wipe in TWRP (except internal/external storage) and see if it boots to CM. Then post what's working and what's not
Enjoy if it works!
Gotta go
Shaheer said:
In school atm, but had a few mins so I built this: https://drive.google.com/file/d/0B5kaDFDMK0TYci14Nm1EOFFnX2s/edit?usp=sharing
Can't reply to any question atm but will when I get home. Not sure if it will boot.
Download, advance wipe in TWRP (except internal/external storage) and see if it boots to CM. Then post what's working and what's not
Enjoy if it works!
Gotta go
Click to expand...
Click to collapse
Great initiative,
I tried making an install. Unfortunately everything halts at the cm welcome screen with the message "Unfortunately, the process com.android.phone has stopped", Maybe, I'm not too surprised since we're using a wifi-version. But, it actually boots up, so there are great expectations for a cm11 port, within short.
Thanks for all your efforts.
arcadia2uk said:
Great initiative,
I tried making an install. Unfortunately everything halts at the cm welcome screen with the message "Unfortunately, the process com.android.phone has stopped", Maybe, I'm not too surprised since we're using a wifi-version. But, it actually boots up, so there are great expectations for a cm11 port, within short.
Thanks for all your efforts.
Click to expand...
Click to collapse
Hey everyone,
So here is an update: (At school so don't have much time but...) This should fix the phone error. :good: However, I am pretty sure Wi-Fi isn't going to work ATM. Since i'm at school can't download things internet is tooo slow, so what someone can do if they want is to download a touchwiz rom for your device or just plain stock rom. Then, on the download go to /system/etc and there should be a folder called Wi-Fi. Copy that to system/etc in the CM rom. And then flash the CM Rom. If Wi-Fi works go ahead and upload the link and post it here.
Download: https://drive.google.com/file/d/0B5kaDFDMK0TYRmNGUVUxVDloeWc/edit?usp=sharing
Shaheer said:
Hey everyone,
So here is an update: (At school so don't have much time but...) This should fix the phone error. :good: However, I am pretty sure Wi-Fi isn't going to work ATM. Since i'm at school can't download things internet is tooo slow, so what someone can do if they want is to download a touchwiz rom for your device or just plain stock rom. Then, on the download go to /system/etc and there should be a folder called Wi-Fi. Copy that to system/etc in the CM rom. And then flash the CM Rom. If Wi-Fi works go ahead and upload the link and post it here.
Download: https://drive.google.com/file/d/0B5kaDFDMK0TYRmNGUVUxVDloeWc/edit?usp=sharing
Click to expand...
Click to collapse
Just as you suspected the wifi didn't work initially. However, I followed your instructions for the update, and there it was. Here's the link to the updated cm11-4.4.4 w. wifi Currently, there seems to be no access to the internal SD card, as well as the external.
I also have difficulties in finding a compatible gapps, any ideas? Could it be due to the SD card issue? It starts up, but playstore crashes at first search.
arcadia2uk said:
Just as you suspected the wifi didn't work initially. However, I followed your instructions for the update, and there it was. Here's the link to the updated cm11-4.4.4 w. wifi Currently, there seems to be no access to the internal SD card, as well as the external.
I also have difficulties in finding a compatible gapps, any ideas? Could it be due to the SD card issue? It starts up, but playstore crashes at first search.
Click to expand...
Click to collapse
Will post an answer in a while. Leaving school in a min so I was just checking the thread. :fingers-crossed:
After homework and all that i'll upload the updated file when I get a chance to work on it.
Shaheer said:
Will post an answer in a while. Leaving school in a min so I was just checking the thread. :fingers-crossed:
After homework and all that i'll upload the updated file when I get a chance to work on it.
Click to expand...
Click to collapse
Great start Shaheer, apparently I'm running into a lot of the same problems that you initially ran into building the T-520 port.
Could I suggest that you start a thread in the development section for this ROM? I believe that I'm one of the few people having noticed your work, and that's only due to your message. Then we can get a few more people to chip in for heavy testing, at least the initial runs.
It would be good if the gapps along with the SDcard and PC-mount issues could have priority. Once they're up you can at least flash back and forth from the same ROM, without passing through an intermediary stock ROM. Notably, as each flash takes close to 30 min, if not more...However, I can believe they are all the result of the fact that the ROM can't detect the internal SDcard; no card = no mount, no card = no play store download.
On the good side, it seems like the GPS is working, and the bluetooth discovers surrounding devices and besides the mentioned SDcard issue, I have not seen much missing at least mot that can be tested at this point. There's no camera, but that seems to be something most AOSP ROM's for the Samsung tablets are struggling with currently.
Anyway, thanks again, I really appreciate your efforts.
arcadia2uk said:
Great start Shaheer, apparently I'm running into a lot of the same problems that you initially ran into building the T-520 port.
Could I suggest that you start a thread in the development section for this ROM? I believe that I'm one of the few people having noticed your work, and that's only due to your message. Then we can get a few more people to chip in for heavy testing, at least the initial runs.
It would be good if the gapps along with the SDcard and PC-mount issues could have priority. Once they're up you can at least flash back and forth from the same ROM, without passing through an intermediary stock ROM. Notably, as each flash takes close to 30 min, if not more...However, I can believe they are all the result of the fact that the ROM can't detect the internal SDcard; no card = no mount, no card = no play store download.
On the good side, it seems like the GPS is working, and the bluetooth discovers surrounding devices and besides the mentioned SDcard issue, I have not seen much missing at least mot that can be tested at this point. There's no camera, but that seems to be something most AOSP ROM's for the Samsung tablets are struggling with currently.
Anyway, thanks again, I really appreciate your efforts.
Click to expand...
Click to collapse
Hey!,
So I was really busy yesterday evening writing a 3 page essay and doing other homework so I didn't get anytime to work on the rom. My thoughts too were to start a new thread in the dev section for this.
I haven't gotten too far with the T520 port either as i'm still learning CM development. (I'm more used to touchwiz ) I have some time right now so give me a bit and i'll try to get a thread started and update the rom to get SD Card working.
EDIT: Actually, I can't proceed till someone can make sure that Google Play downloads app properly. If it doesn't then I need to work on that before anything or it's going to cause major issues.
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