Related
This is a strange problem that I only started to have once I installed Team Nekkid 7.2 RC dated 3/29.
I can flash the ROM no problem, wipe dalvik and fix permissions and I'm good to go without any issues. But if I flash the ROM, then either morfic or faux kernel, then gapps, when I go to wipe dalvik, all I get is a quick screen flash with no option to actually wipe dalvik.
I go back and wipe the overall cache completely, fix permissions, the reboot. I am now stuck at the morfic boot animation until i pull battery.
If i try to install a Faux kernel, same thing happens with dalvik, but gets stuck at the blue LG screen.
Once i battery pull and get back to CWM, i wipe everything, reflash ROM and gapps, wipe dalvik and fix permissions no problem and boot up into whatever ROM i choose.
EDIT: Went back and flashed Bionix 1.4.1 and was able to flash a Faux kernel and wipe dalvik. Booting up this ROM now.
I also have NO problem with ICS ROMS/kernels.
When you say NO PROBLEMS with ICS ROMs, does that include Google Maps and the stock browser working perfectly??
Which ICS ROMs have you tried? How is battery life?
Thanks!
Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium
mt3g said:
Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I did all of that. I flashed the kernel before and after gapps but end up with the same result.
I have a feeling there is an issue with the CWM since I am constantly flashing roms/kernels and have never had these problems before. I'm at work so I cant use the Nvidia tool to flash CWM so I have to wait until I get home.
mariuscm said:
When you say NO PROBLEMS with ICS ROMs, does that include Google Maps and the stock browser working perfectly??
Which ICS ROMs have you tried? How is battery life?
Thanks!
Click to expand...
Click to collapse
I meant I have no problem flashing ICS roms and kernels.
mt3g said:
Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I usually just follow the instructions precisely by the OP. (Wiping/formatting, flashing rom, gapps, restart + let 10 min stand if required by OP) I have not installed another kernel that what the ROM has included. Should I try that? If yes, which one? I currently have EGB AOSP ICS 4.0.4
[UPDATE] Ok I got it now. Just read your last message
mariuscm said:
I usually just follow the instructions precisely by the OP. (Wiping/formatting, flashing rom, gapps, restart + let 10 min stand if required by OP) I have not installed another kernel that what the ROM has included. Should I try that? If yes, which one? I currently have EGB AOSP ICS 4.0.4
Click to expand...
Click to collapse
Short answer: yes, install a different ROM
Long answer: go to the developing section of the G2X forums and find out the info with the countless threads.
stevew84 said:
Short answer: yes, install a different ROM
Long answer: go to the developing section of the G2X forums and find out the info with the countless threads.
Click to expand...
Click to collapse
I've tried 3 different ICS roms and read hundreds of posts and found nothing that would fix the maps and browser issues. I guess I have to wait a bit more for the devs to work on them. Maybe the lack of drivers is the problem.
mariuscm said:
I've tried 3 different ICS roms and read hundreds of posts and found nothing that would fix the maps and browser issues. I guess I have to wait a bit more for the devs to work on them. Maybe the lack of drivers is the problem.
Click to expand...
Click to collapse
Look for Owain's Unnoficial Build 55 thread, and use Firefox browser, that is the most complete ICS ROM and Firefox doesnt have the rotation problem.
stevew84 said:
Look for Owain's Unnoficial Build 55 thread, and use Firefox browser, that is the most complete ICS ROM and Firefox doesnt have the rotation problem.
Click to expand...
Click to collapse
I was just downloading that ROM
Thanks!
My main concern is Google Maps not working properly. I rely on it in my job a lot and can't have it blanking out on me like that.
I've tried the replacement solution for the stock browser - I installed Dolphin HD. I'll try Firefox, though. Haven't used that on a phone since I had the Nokia N900 - Ah, the good times when I still believed in Nokia
Thanks for your help!
mariuscm said:
I was just downloading that ROM
Thanks!
My main concern is Google Maps not working properly. I rely on it in my job a lot and can't have it blanking out on me like that.
I've tried the replacement solution for the stock browser - I installed Dolphin HD. I'll try Firefox, though. Haven't used that on a phone since I had the Nokia N900 - Ah, the good times when I still believed in Nokia
Thanks for your help!
Click to expand...
Click to collapse
If the maps shows up and then goes blank, simply close the map and re-open it.
I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.
mariuscm said:
I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.
Click to expand...
Click to collapse
All the important information will be in the first post of his thread. he doesn't include a change log, though.
mariuscm said:
I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.
Click to expand...
Click to collapse
Yes, it's 4.0.4 with all of the latest CM9 commits.
Sent from my LG-P999 using xda premium
Ive had enough of running buggy, battery hungry roms and would like to return my Nexus S to stock. The last time I was on stock was 2.3.6 I believe. If I flash via CWM to the official 4.0.3 in this thread: http://forum.xda-developers.com/showthread.php?t=1445570 will I then be able receive OTA updates, ie to 4.1.2? (obviously Ill be rooted again, but im not fussed)
Rotellian said:
Ive had enough of running buggy, battery hungry roms and would like to return my Nexus S to stock. The last time I was on stock was 2.3.6 I believe. If I flash via CWM to the official 4.0.3 in this thread: http://forum.xda-developers.com/showthread.php?t=1445570 will I then be able receive OTA updates, ie to 4.1.2? (obviously Ill be rooted again, but im not fussed)
Click to expand...
Click to collapse
Flash the stock images from Google and 4.1.2 instead.
https://developers.google.com/android/nexus/images#sojujzo54k
Read the instructions, you need to use fastboot for these.
polobunny said:
Flash the stock images from Google and 4.1.2 instead.
https://developers.google.com/android/nexus/images#sojujzo54k
Read the instructions, you need to use fastboot for these.
Click to expand...
Click to collapse
Best way to do it!
Rotellian said:
Ive had enough of running buggy, battery hungry roms and would like to return my Nexus S to stock. The last time I was on stock was 2.3.6 I believe. If I flash via CWM to the official 4.0.3 in this thread: http://forum.xda-developers.com/showthread.php?t=1445570 will I then be able receive OTA updates, ie to 4.1.2? (obviously Ill be rooted again, but im not fussed)
Click to expand...
Click to collapse
Buggy? Battery hungry ? You were in what ROM? All custom ROMs at almost 100% bugs free(especially CM10 and CM10/AOKP based). Weird ...
Dont have the time to setup the computer for Fastboot, couldnt get it working with Win7 last time out either.
aladin6 said:
Buggy? Battery hungry ? You were in what ROM? All custom ROMs at almost 100% bugs free(especially CM10 and CM10/AOKP based). Weird ...
Click to expand...
Click to collapse
Tried all sorts, Oxygen, NSCollab, early ICS roms (awful), others i cant remember. Best combo i had was stock 2.3.6/7 with a Kernel i think. I found that invariably they become less stable the longer you have them installed. Of course if you change rom a lot you'll never notice.
I'm with you, running stock 4.1.2 since it came out, only with custom kernel for BLN, highbigmem and voodoo sound and don't regret it a bit. A lot of free time and no need to update all the time;P
Rotellian said:
Dont have the time to setup the computer for Fastboot, couldnt get it working with Win7 last time out either.
Click to expand...
Click to collapse
How did you root and unlock your phone then? Only way to do it needs an actual working connection with fasboot/adb. Even the 1 click crap uses that.
I guess nothing stops you from flashing 4.0.3 then going the upgrade route, but I don't see that as a very efficient nor a clean way to do it.
madd0g said:
I'm with you, running stock 4.1.2 since it came out, only with custom kernel for BLN, highbigmem and voodoo sound and don't regret it a bit. A lot of free time and no need to update all the time;P
Click to expand...
Click to collapse
OMG, how can you stay with ONE ROM more than one week . No seriously, there is 2 ROMs that they're perfectly stable and full of features: CM10 and ParanaoidAndroid. I no longer look to other ROMs. And ParanoidAndroid is in my device more than 2 weeks
aladin6 said:
OMG, how can you stay with ONE ROM more than one week . No seriously, there is 2 ROMs that they're perfectly stable and full of features: CM10 and ParanaoidAndroid. I no longer look to other ROMs. And ParanoidAndroid is in my device more than 2 weeks
Click to expand...
Click to collapse
It would be hard to call CM10 something related to stable (same for any CM10 base ROM). Even they don't call it that. That's why the nightly tag is for.
polobunny said:
It would be hard to call CM10 something related to stable (same for any CM10 base ROM). Even they don't call it that. That's why the nightly tag is for.
Click to expand...
Click to collapse
Other than "stable" "nightly" "RC" WORDS, CM10 is completely STABLE(at 99%). And i know what "stable" word means. Source: own experience .
polobunny said:
How did you root and unlock your phone then? Only way to do it needs an actual working connection with fasboot/adb. Even the 1 click crap uses that.
I guess nothing stops you from flashing 4.0.3 then going the upgrade route, but I don't see that as a very efficient nor a clean way to do it.
Click to expand...
Click to collapse
Managed to get ADB working on my old XP laptop, which i no longer have! Just tried to install it, and again the driver problem rears its ugly head. Just wont recognise the inf file! Like I said, dont really have the time, guess ill just have to flash to 4.0.3 and wait for the OTA Dont have the time to muck about trying to get the drivers working. Might give it one last bash with the SDK
Rotellian said:
Dont have the time to setup the computer for Fastboot, couldnt get it working with Win7 last time out either.
Click to expand...
Click to collapse
Returning to stock requires a computer. Official OTA updates will not install without the stock recovery.
Sent from my Nexus S 4G using Tapatalk 2
aladin6 said:
Other than "stable" "nightly" "RC" WORDS, CM10 is completely STABLE(at 99%). And i know what "stable" word means. Source: own experience .
Click to expand...
Click to collapse
You'll see a lot of people still have complaints regarding functions that get broken with each version, only to come back working after the next one. It's silly to assume CM team doesn't know **** about development and simply tag "nightly", "RC" and "stable" for the sake of it. Please don't bring up made up stability percentages into the lot.
You can glance at the nightly changelogs yourself to see NPEs getting corrected in relatively core apps nearly every week. Not just for crespo too, but regarding CM10 as a whole.
I'll give you that though, on a day to day basis, the rom is very usable. But good luck getting a 1000 hours uptime without the thing becoming sluggish.
Rotellian said:
Managed to get ADB working on my old XP laptop, which i no longer have! Just tried to install it, and again the driver problem rears its ugly head. Just wont recognise the inf file! Like I said, dont really have the time, guess ill just have to flash to 4.0.3 and wait for the OTA Dont have the time to muck about trying to get the drivers working. Might give it one last bash with the SDK
Click to expand...
Click to collapse
Just get the PDAnet Android drivers.
madd0g said:
Just get the PDAnet Android drivers.
Click to expand...
Click to collapse
Was just going to do that, but think ive got it working now. Im guessing a full install from google's image will result in a compeltely stock phone including bootloader?
lol
Rotellian said:
Ive had enough of running buggy, battery hungry roms and would like to return my Nexus S to stock. The last time I was on stock was 2.3.6 I believe. If I flash via CWM to the official 4.0.3 in this thread: http://forum.xda-developers.com/showthread.php?t=1445570 will I then be able receive OTA updates, ie to 4.1.2? (obviously Ill be rooted again, but im not fussed)
Click to expand...
Click to collapse
lol, really you want to go back to stock?
wats buggy now?
stable roms of ics,gb came in...
I'm using this now: http://forum.xda-developers.com/showthread.php?t=1946338 . It'a a 4.1.2 stock rom, just flash it and you're ready to go.
---------- Post added at 11:31 PM ---------- Previous post was at 11:28 PM ----------
unnamed.aj. said:
lol, really you want to go back to stock?
wats buggy now?
stable roms of ics,gb came in...
Click to expand...
Click to collapse
For me, cm10 m2 was buggy and slow. So I had decided to return to 4.1.2 stock (with Matrix kernel )
sergiu_s said:
I'm using this now: http://forum.xda-developers.com/showthread.php?t=1946338 . It'a a 4.1.2 stock rom, just flash it and you're ready to go.
---------- Post added at 11:31 PM ---------- Previous post was at 11:28 PM ----------
For me, cm10 m2 was buggy and slow. So I had decided to return to 4.1.2 stock (with Matrix kernel )
Click to expand...
Click to collapse
Cheers, looks good Does it include radio? Just flash with CWM?
Rotellian said:
Was just going to do that, but think ive got it working now. Im guessing a full install from google's image will result in a compeltely stock phone including bootloader?
Click to expand...
Click to collapse
If you use all commands from the flash-all.sh script, yes. No need to flash the bootloader and radio if you already have the latest version.
I've been having issues with all sound dropping out on various ROMs and I don't recall this happening on any pre-3.4 kernel based ROMs.
All the download links in the threads for 4.2.2 ROMs are now dead so I was wondering if anyone has an old file kicking around? Or know where I could find one? My hard drive died a while back and it seems everything since then has been 3.4 based so I no longer have any 3.0 ROMs on my computer that I can try myself.
Any help or direction would be greatly appreciated. Thanks.
DRUMROT said:
I've been having issues with all sound dropping out on various ROMs and I don't recall this happening on any pre-3.4 kernel based ROMs.
All the download links in the threads for 4.2.2 ROMs are now dead so I was wondering if anyone has an old file kicking around? Or know where I could find one? My hard drive died a while back and it seems everything since then has been 3.4 based so I no longer have any 3.0 ROMs on my computer that I can try myself.
Any help or direction would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
man, people prefer 3.4 and u want to go back to 3.0 lol
PandaPower said:
man, people prefer 3.4 and u want to go back to 3.0 lol
Click to expand...
Click to collapse
Haha, yeah, I know. But when your phone has no sound whatsoever, it ceases to be useful. Can't remember that happenign to me on 3.0 so I figured I'd check it out.
Also, not too sure what the big deal is with 3.4. When it first came out, there was the wake lag, then that was fixed but bootloops became an issue. The 3.0 ROMs were more reliable for me in general, just not as up to date.
EDIT: Your first post ever was to tell me that? Haha
Here you go:
Liquid Smooth v2.4
Android 4.2.2
Gapps included
Twisted IV kernel included
Built by $droyd$ 23/05/13
https://drive.google.com/file/d/0B_VcoEHi3OfvalB1ZXh5MkhucUk/edit?usp=sharing
An old favourite and one of the best ROM's for this phone. I have Twisted V & VI as well, just let me know if you need them.
rosswhite said:
Here you go:
Liquid Smooth v2.4
Android 4.2.2
Gapps included
Twisted IV kernel included
Built by $droyd$ 23/05/13
https://drive.google.com/file/d/0B_VcoEHi3OfvalB1ZXh5MkhucUk/edit?usp=sharing
An old favourite and one of the best ROM's for this phone. I have Twisted V & VI as well, just let me know if you need them.
Click to expand...
Click to collapse
If this works you'll be my bestest friend, haha. I didn't think this was going to happen. Thanks so much.
Are V and VI 3.0 based?
THANK YOU
Ok so it sort of works.
No sound issues so far but I keep getting random soft reboots and apps constantly closing (no error or pop up), Cleared caches in recovery. Anything special I'm supposed to do after flashing this? I'm so close to having a working phone again, this ROM seems likes my best bet...but now it's giving me other issues.
Thank you for your time.
Try changing skin on the phone and then change it back also for soft reboots what works for me is uninstallin kernel Turner and reinstalling and applying settings again
Sent from my HTC One S using xda app-developers app
Accountban said:
Try changing skin on the phone and then change it back also for soft reboots what works for me is uninstallin kernel Turner and reinstalling and applying settings again
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Thanks, I'll give it a whirl when I get a chance.
DRUMROT said:
If this works you'll be my bestest friend, haha. I didn't think this was going to happen. Thanks so much.
Are V and VI 3.0 based?
THANK YOU
Click to expand...
Click to collapse
DRUMROT said:
Ok so it sort of works.
No sound issues so far but I keep getting random soft reboots and apps constantly closing (no error or pop up), Cleared caches in recovery. Anything special I'm supposed to do after flashing this? I'm so close to having a working phone again, this ROM seems likes my best bet...but now it's giving me other issues.
Thank you for your time.
Click to expand...
Click to collapse
Yeah, according to his thread all the Twisted kernel's were based on 3.0.
http://forum.xda-developers.com/showthread.php?t=2232515&highlight=twisted
Links for the kernel's below:
Twisted V: https://drive.google.com/file/d/0B_VcoEHi3OfvbmlsLWZhSVF0YnM/edit?usp=sharing
Twisted VI: https://drive.google.com/file/d/0B_VcoEHi3OfvYW1XcE1ueklMUGM/edit?usp=sharing
I can't really remember but I don't think there was any special instructions to install Liquid Smooth. Check the thread:
http://forum.xda-developers.com/showthread.php?t=2194095&highlight=liquid+smooth
You might want to try this ROM as well: https://drive.google.com/file/d/0B_VcoEHi3OfvSnh3djJTTjMtdHM/edit?usp=sharing
No thread for it because it had to be taken down, but ran as well as Liquid did. Not sure if Gapps are included.
rmbq still has some v3.0 kernel's for download here: http://www.androidfilehost.com/?w=files&flid=3224
Try bubba Vn5 if you're still having problems.
rosswhite said:
Yeah, according to his thread all the Twisted kernel's were based on 3.0.
http://forum.xda-developers.com/showthread.php?t=2232515&highlight=twisted
Links for the kernel's below:
Twisted V: https://drive.google.com/file/d/0B_VcoEHi3OfvbmlsLWZhSVF0YnM/edit?usp=sharing
Twisted VI: https://drive.google.com/file/d/0B_VcoEHi3OfvYW1XcE1ueklMUGM/edit?usp=sharing
I can't really remember but I don't think there was any special instructions to install Liquid Smooth. Check the thread:
http://forum.xda-developers.com/showthread.php?t=2194095&highlight=liquid+smooth
You might want to try this ROM as well: https://drive.google.com/file/d/0B_VcoEHi3OfvSnh3djJTTjMtdHM/edit?usp=sharing
No thread for it because it had to be taken down, but ran as well as Liquid did. Not sure if Gapps are included.
rmbq still has some v3.0 kernel's for download here: http://www.androidfilehost.com/?w=files&flid=3224
Try bubba Vn5 if you're still having problems.
Click to expand...
Click to collapse
I love this community. Not going to have the chance to mess with this until tomorrow probably, but I will post and let you know how it all goes. Really appreciate the help.
EDIT: I read through that thread yesterday and it doesn't seem like there's anything special I need to do, so hopefully some of these other suggestions work. Once I flash it again I'll try changing the governor (if I can make it that far without rebooting, haha). If that doesn't work, you've given me lots to work with. Thanks.
I have a blackbean build with the 3.0 kernel.
Sent from my One S using Tapatalk
rosswhite said:
Yeah, according to his thread all the Twisted kernel's were based on 3.0.
http://forum.xda-developers.com/showthread.php?t=2232515&highlight=twisted
Links for the kernel's below:
Twisted V: https://drive.google.com/file/d/0B_VcoEHi3OfvbmlsLWZhSVF0YnM/edit?usp=sharing
Twisted VI: https://drive.google.com/file/d/0B_VcoEHi3OfvYW1XcE1ueklMUGM/edit?usp=sharing
I can't really remember but I don't think there was any special instructions to install Liquid Smooth. Check the thread:
http://forum.xda-developers.com/showthread.php?t=2194095&highlight=liquid+smooth
You might want to try this ROM as well: https://drive.google.com/file/d/0B_VcoEHi3OfvSnh3djJTTjMtdHM/edit?usp=sharing
No thread for it because it had to be taken down, but ran as well as Liquid did. Not sure if Gapps are included.
rmbq still has some v3.0 kernel's for download here: http://www.androidfilehost.com/?w=files&flid=3224
Try bubba Vn5 if you're still having problems.
Click to expand...
Click to collapse
OK, been busy all weekend so here's my findings:
I was able to get Liquid Smooth working using the Bubba Vn5 kernel. That was the first step.
Then I had to give it time and see if my audio dropped - and it did. So the 3.4 kernel doesn't seem to be the issue.
So I ran a logcat and while not completely versed in what to look for, I did find some audio errors relating to the audiopolicy manager, and tone generator and soundpool. Did a bit of searching and seems it could have to do with my firmware, which, of course, was also switched when I changed to the 3.4 kernel. I'm going to try reflashing 2.15 and maybe upgrade to 2.16 if that doesn't work. If neither work, I'll have to see about downgrading, but since I don't have a lower flashable zip, I'll have to mess around with an RUU so hopefully it doesn't come to that.
Thanks to everyone. At the very least, you're helping me eliminate possible causes.
Darknites said:
I have a blackbean build with the 3.0 kernel.
Sent from my One S using Tapatalk
Click to expand...
Click to collapse
If I can get my sound back I'll probably be sticking with a 3.0 based rom as at the very least I'm not constantly plagued by bootloops so I'll gladly take your copy of blackbean if you don't mind. Just another option for me to flash
p.s: my logcat should be attached. If anyone has experience with reading them, it would be greatly appreciated if you could take a look and see if anything stands out. Thanks again to everybody.
Ok, so I managed to extract the ruu using a script and flashed the rom.zip via fastboot. I am now on hboot 1.13, running LS v2.4 with bubba vn5 (3.0 kernel) and am still without sound. Logcat shows the same errors as the one I posted above (not sure exactly what they mean, but they are audio related from what I can tell.
Since I have ruled out everything I can think of on the software side, could this possible be a hardware issue?
DRUMROT said:
If I can get my sound back I'll probably be sticking with a 3.0 based rom as at the very least I'm not constantly plagued by bootloops so I'll gladly take your copy of blackbean if you don't mind. Just another option for me to flash
p.s: my logcat should be attached. If anyone has experience with reading them, it would be greatly appreciated if you could take a look and see if anything stands out. Thanks again to everybody.
Click to expand...
Click to collapse
Just here dude and looking at logcat to me look like you got no drivers or no sound hardware, not like that's any use to you.
Darknites said:
Just here dude and looking at logcat to me look like you got no drivers or no sound hardware, not like that's any use to you.
Click to expand...
Click to collapse
Thanks, based on my searches, it seemed like every older ROM had dead links.
No drivers or sound hardware, huh? So something isn't right, haha. I've had sound at points so I assume there must be something up with how the software interacts with the hardware or my hardware isn't stable and works only from time to time.
Not what I wanted to hear but what can ya do? I've posted this in the Q and A forum as well, see if I can get some more info. Thanks though.
DRUMROT said:
Thanks, based on my searches, it seemed like every older ROM had dead links.
No drivers or sound hardware, huh? So something isn't right, haha. I've had sound at points so I assume there must be something up with how the software interacts with the hardware or my hardware isn't stable and works only from time to time.
Not what I wanted to hear but what can ya do? I've posted this in the Q and A forum as well, see if I can get some more info. Thanks though.
Click to expand...
Click to collapse
Ya I'm in no rush to delete it. I would go with an hardware issue but have you tried a Sense rom?
Darknites said:
Ya I'm in no rush to delete it. I would go with an hardware issue but have you tried a Sense rom?
Click to expand...
Click to collapse
Got it downloaded
I've tried the newer, 4.2.2 Sense ROMs and while not entirely sure (I wasn't really looking for the sound issue at the time) I recall it happening on them, too.
But I'm going to try the old ViperOneS 4.1.2 ROM because I know that I had no issues at all back when I was using that. If it's still present, I'm going to assume it's a hardware fault and I'll have to try and unroot, s-on, go back to stock, achange my CID and all that crap and see if I can't get it replaced.
Thanks for your help.
DRUMROT said:
Got it downloaded
I've tried the newer, 4.2.2 Sense ROMs and while not entirely sure (I wasn't really looking for the sound issue at the time) I recall it happening on them, too.
But I'm going to try the old ViperOneS 4.1.2 ROM because I know that I had no issues at all back when I was using that. If it's still present, I'm going to assume it's a hardware fault and I'll have to try and unroot, s-on, go back to stock, achange my CID and all that crap and see if I can't get it replaced.
Thanks for your help.
Click to expand...
Click to collapse
If you still have issue then ya send it back but remember to use an RUU before S-On.
Darknites said:
If you still have issue then ya send it back but remember to use an RUU before S-On.
Click to expand...
Click to collapse
Yeah, I'm too anal to not read things 50 times before attempting it so I'll check out some guides and everything before I try to go back to stock.
Thanks again.
Q&A for [KERNEL][ALPHA][LP 5.1]CyanogenMod 12.1 Kernel with DoubleTap2Wake
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][ALPHA][LP 5.1]CyanogenMod 12.1 Kernel with DoubleTap2Wake. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Bootloop after flashing. Help!
Need some help. I have installed this kernel on CM 12.1 Rohan's build and got bootloop... Some info: I used Philz Touch 6 Fota and wiped cache and dalvic after flash. I recovered from soft brick through but what should I do to avoid bootloop?
File
Sorry for the dumb question but what is zip dl-0? cant flash it, it wont detect it.
Good day. First off, i wanted to say that i've tried this kernel and the d2w is very helpful for preserving the hw power button and i think this kernel is very useful.
The thing is, since their latest releases, i've found that Glade Rom and SlimLP have been the roms that are best for me in terms of what i need and my daily usage. Unfortunately, this kernel doesn't work for either of them. I'm guessing it's because of their base?
Anyway, i'd like to ask if the dev has any plans to get this kernel working for either of those roms or for aosp 5.1.1 roms in general? If yes, that would be awesome. If not, then i still say this kernel's features are still very helpful and i'll be waiting to get a cm-based rom that works for my needs. ?
cascabel said:
Good day. First off, i wanted to say that i've tried this kernel and the d2w is very helpful for preserving the hw power button and i think this kernel is very useful.
The thing is, since their latest releases, i've found that Glade Rom and SlimLP have been the roms that are best for me in terms of what i need and my daily usage. Unfortunately, this kernel doesn't work for either of them. I'm guessing it's because of their base?
Anyway, i'd like to ask if the dev has any plans to get this kernel working for either of those roms or for aosp 5.1.1 roms in general? If yes, that would be awesome. If not, then i still say this kernel's features are still very helpful and i'll be waiting to get a cm-based rom that works for my needs. ?
Click to expand...
Click to collapse
Doesn't work in the sense?
I have plans to bring this to every LP based ROM for XL.
I guess there might be some kernel related change. I will see to it.
corphish said:
Doesn't work in the sense?
I have plans to bring this to every LP based ROM for XL.
I guess there might be some kernel related change. I will see to it.
Click to expand...
Click to collapse
bootloops. even through a clean install or flashing it after an install and clearing dalvik and cache...
i've noticed that the roms that doesn't work with tz 4.15 won't work with this kernel either.
great to hear your plans. really appreciate it.
edit:
both these roms are aosp based and have RRO supported as opposed to cm theme engine. could that have any bearing on it? let me know how i can help.
Problem on my HTC One (M7)
Hello,
first of all I would like to apologize for my English problems. I installed your Kernel on my HTC ONE M7. It is running on Cyanogenmod 12.1 (Android 5.1.1). The problem is that my handy freezes everytime it tries to boot. It freezes on the HTC logo to be more specific. Please let me know if you need to know more details or need even a log and I hope this issue gets solved.
Thank you
usb619 said:
Hello,
first of all I would like to apologize for my English problems. I installed your Kernel on my HTC ONE M7. It is running on Cyanogenmod 12.1 (Android 5.1.1). The problem is that my handy freezes everytime it tries to boot. It freezes on the HTC logo to be more specific. Please let me know if you need to know more details or need even a log and I hope this issue gets solved.
Thank you
Click to expand...
Click to collapse
LOL No, this kernel is not meant for HTC One.
This kernel is only for Sony Xperia L. Please read the full post before trying anything.
Now how to recover? If you are able to go in recovery, flash CM12 or any custom ROM.
Master Solution is flashing stock as always, although I dont know how things are done for HTC [emoji14]
@corphish i kniw i shouldn't but.. If it's possible, may i ask that you add the Intelliactive scheduler if you can? Lulzactive and on demand doesn't really work for me (lulzactive seemed buggy last time i tried it - main core stayed on max freq). Just a request. ?
Wifi stopped working after I flashed this kernel. Previously I was on Tz 4.16. Any ideas what I can do fix this, other than going back to Tz?
primemonitor said:
Wifi stopped working after I flashed this kernel. Previously I was on Tz 4.16. Any ideas what I can do fix this, other than going back to Tz?
Click to expand...
Click to collapse
Well, you cannot go back to TZ now. It flashes kernel in boot-device linked partition, which is a mystery partition about which only Varun knows.
I haven't succeeded in your situation.
Sent from my C2104 using Tapatalk
corphish said:
Well, you cannot go back to TZ now. It flashes kernel in boot-device linked partition, which is a mystery partition about which only Varun knows.
I haven't succeeded in your situation.
Sent from my C2104 using Tapatalk
Click to expand...
Click to collapse
Right, learned that the hard way
Is this a known issue though, or something that you or others have previously faced, that changing from Tz to Zapdos will break wifi? Just curious.
Hey man, I use Primexperia rom, it's CM12 based, soon to be posted new ver CM12.1 based. For some reasons it's not compatible with TZ 4.16, 4.14 only (wi fi missing on 4.16) Will this kernel work for me? The only thing I really need is a stable system with Sony sound
Oh almost forgot, I use TWRP and I think that any other recovery is a waste of time, to be honest. Can I use TWRP?
illague said:
Hey man, I use Primexperia rom, it's CM12 based, soon to be posted new ver CM12.1 based. For some reasons it's not compatible with TZ 4.16, 4.14 only (wi fi missing on 4.16) Will this kernel work for me? The only thing I really need is a stable system with Sony sound
Oh almost forgot, I use TWRP and I think that any other recovery is a waste of time, to be honest. Can I use TWRP?
Click to expand...
Click to collapse
I tried, breaks network .
Sent from my C2104 using Tapatalk
corphish said:
I tried, breaks network .
Sent from my C2104 using Tapatalk
Click to expand...
Click to collapse
Stryder modded the rom while he had TZ installed ... I dont get why but thats it... Flash TZ4.15 and then TZ4.16
Sent from my Xperia T using XDA Free mobile app
Stryflex LP 1.5 Rom
Hi,
I am using Stryflex LP 1.5 Rom.
When used the its kernel,phone freezes randomly & hangs & not responds.
We have to take out battery & restart phone.
Most of the times even if i take out from pocket also it is in DeadState(even if pressed power button alos nothing works.)
So i installed Thunderzap 4.16 ,it is not freezing but Wifi is not working.
Then i shifted to your kernel, thank god it is not at all freezing while operating .
But i noticed that it is going to black screen/Dead State very frequently.
Waiting for any suggestions & help.
I appreciate your help & time.
Could we get 1.7~ OC like in TZ kernel? It was fully stable for me even with thermal throttling disabled.
Maybe it's noob but would the wake up signatures Hurt the touchscreen some how.
I mean it well make it work for 24 hour????
Tz 4.16 with cm 12 work properly and Wi-Fi is goog and with application tenderzap control you can Cheng setting so good and you can change control charge to 2100 ma for faster charging so download tanderzap control.apk
Sent from my C2105 using Tapatalk
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
After installing rom should install tanderzap.zip with via recovery for resolve Wi-Fi problem
Sent from my C2105 using Tapatalk
This thread is for updates of temasek cm12.1 built by myself. I will be building for hlte and hltespr.
Temasek made this all possible and it is all his work I am just taking the time to build and upload.
V19.3+ root removed, you will need to flash SuperSU zip to achieve root.
Downloads:
Hlte or Hlte on my BasketBuild
Hltespr or Hltespr on my BasketBuild
Credits: @temasek
XDA:DevDB Information
Temasek cm-12.1 unofficial cyanogenmod, ROM for the Samsung Galaxy Note 3
Contributors
trader418, Temasek
Source Code: https://github.com/temasek/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: Cyanogenmod
Version Information
Status: Beta
Created 2016-03-26
Last Updated 2016-03-26
Thanks for keeping support for the Note 3 alive.
Great, good to see 12.1 back alive. Anything I can do to help, just say so.
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Buslova said:
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Click to expand...
Click to collapse
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Straw poll whether to include root in the build here http://strawpoll.me/7191529
trader418 said:
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Click to expand...
Click to collapse
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Buslova said:
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Click to expand...
Click to collapse
Ota isn't too bad, I'll probably use it soon tbh, but I won't promise anything
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
redfuryjr55 said:
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
Click to expand...
Click to collapse
Start with which device you have
trader418 said:
Start with which device you have
Click to expand...
Click to collapse
haha sorry! htlespr!
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
trader418 said:
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
Click to expand...
Click to collapse
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
redfuryjr55 said:
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
Click to expand...
Click to collapse
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
trader418 said:
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
Click to expand...
Click to collapse
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
swukjay said:
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
Click to expand...
Click to collapse
Either change weather provider to another or customize your location. Sometimes yahoo weather isn't working well.
As for WiFi, check your dev options.
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
eseregin said:
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
Click to expand...
Click to collapse
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Hmm, still no luck eh? I tried helping ya last night in the other thread. I'm also a hltespr user. I'm still running OH1 baseband however OK2 is the latest. Also, as I told you last night, I'm using an older version of TWRP recovery (ver. 2.8.7) however the latest is 3.0.0.
What baseband are YOU running? Go to settings, "About phone", and look for "Baseband version" and let us know. =)
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Sorry, I have different phone..
Might be the latest here
https://idlekernel.com/flash-tools/firmware/hltespr_SM-N900P/N900PVPUEOK2/
But I am far away from sure